Skip to content

Commit 76f0056

Browse files
committed
troubleshooting renv
1 parent a870cb0 commit 76f0056

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

docs/troubleshooting.md

+22
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,28 @@ For example, in [Posit Connect 2024.12.0](https://docs.posit.co/connect/news/#po
5050
Gradio app support was introduced. When deploying a Gradio app to a server
5151
running an older version of Posit Connect than 2024.12.0, it will error.
5252

53+
### `renv` errors on deployment
54+
55+
When deploying projects using `R`, it is indispensable for the Posit Publisher extension
56+
to have access to a record of the dependencies used by your project.
57+
This record is expected to be found as a `lockfile` (commonly named as `renv.lock`) generated by `renv`,
58+
since the [`renv` package](https://rstudio.github.io/renv/articles/renv.html)
59+
is a great choice to create reproducible environments.
60+
61+
Clarifying things a bit, `renv` is not a requirement, the `lockfile` is.
62+
It is possible to collaborate in projects that already have a `lockfile`
63+
and not having `renv` available in your system.
64+
65+
If there is not a `lockfile`, the Posit Publisher extension will attempt to scan the current state of the project
66+
and provide you with a solution to generate the expected `lockfile`.
67+
68+
![](https://cdn.posit.co/publisher/assets/img/publisher-renv-setup-notification.png)
69+
70+
Solutions provided by the Posit Publisher extension to fix an `renv` environment are limited
71+
to the most common scenarios, any other issue around `renv` and a `lockfile` generation will require
72+
additional attention by you. For those cases the Posit Publisher extension will suggest
73+
to evaluate the situation getting the status of the environment with `renv::status()`.
74+
5375
## Still having trouble?
5476

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

0 commit comments

Comments
 (0)