Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Troubleshooting renv section #2562

Merged
merged 7 commits into from
Jan 29, 2025
Merged
Changes from 6 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,25 @@ For example, in [Posit Connect 2024.12.0](https://docs.posit.co/connect/news/#po
Gradio app support was introduced. When deploying a Gradio app to a server
running an older version of Posit Connect than 2024.12.0, it will error.

## `renv` errors on deployment

When deploying `R` projects, it is essential that Posit Publisher has
access to a record of the dependencies used by your project to reproduce
the project on Posit Connect.
The [`renv` package](https://rstudio.github.io/renv/articles/renv.html) can
create that record as a `lockfile` (commonly named `renv.lock`).

Projects that already include a `lockfile` do not require `renv` be setup.

If an R project doesn't have a `lockfile` on deploy, Posit Publisher prompts to
provide a solution to generate the expected `lockfile`.

![](https://cdn.posit.co/publisher/assets/img/publisher-renv-setup-notification.png)

When uncommon errors occur that Posit Publisher cannot solve for you, it
prompts to evaluate the status of `renv` using
[`renv::status()`](https://rstudio.github.io/renv/reference/status.html).

## Still having trouble?

If you're still having trouble with Posit Publisher or have any questions,
Expand Down