Containerizing an existing renv project | Caching package installs | Basic Docker layer cache | Cache mounts | Bind-mounted host caches | System dependencies | Multi-stage builds

Inferring package sources | Unknown sources | Custom R package repositories | Repository snapshots | Bioconductor | Initializing a project | Bioconductor releases | Bioconductor mirrors | Disabling Bioconductor | The package cellar | Explicit sources | ABI compatibility | Build-time dependencies

Why isn't my package being snapshotted into the lockfile? | Capturing all dependencies | Capturing explicit dependencies | How do I update the lockfile? | How should I handle development dependencies? | I'm returning to an older renv project. What do I do? | How can I check my packages for known vulnerabilities? | Why are package downloads failing?

Cache | Cache location | Multiple caches | Shared cache locations | Caveats | Building from source | Configure flags | Install flags | Vignettes | Downloads | Alternative downloaders | Proxies | Authentication | Azure DevOps | Git and Personal Access Tokens | Custom headers | Debugging

Publishing from the RStudio IDE | Publishing programatically | A word about packrat

Introduction | Usage | Managing profile-specific dependencies | Profile-specific ignore rules

GitHub actions | Using r-lib/actions/setup-renv | Using the GitHub Actions Cache with renv | Generating a lockfile in CI | Downloading packages in CI | GitLab CI

Libraries and repositories | Getting started | Collaboration | Installing packages | Updating packages | Infrastructure | Caveats | Uninstalling renv

Activating Python integration | Deactivating Python integration | Understanding Python integration | Virtual environments | Conda environments

Detecting RStudio | Session Interaction | Running at Startup

Development | Isolation | Library Paths | Testing | Submitting to CRAN

TerminalExecute Scenario | Interative Terminal Scenario | Terminal Identifier | Terminal Session | Busy Terminal | Terminal States