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

Deployments with renv.lock do not preserve renv.lock in content bundle #926

Closed
kmasiello opened this issue Jul 21, 2023 · 2 comments · Fixed by #927
Closed

Deployments with renv.lock do not preserve renv.lock in content bundle #926

kmasiello opened this issue Jul 21, 2023 · 2 comments · Fixed by #927
Assignees

Comments

@kmasiello
Copy link

Push button deployment of simple shiny app with renv.lock included succeeds with renv v 1.0.0.9000 and rsconnect v 1.0.1, however the bundle downloaded from the Source Versions in Connect only has app.R and manifest.json in it. The lock file is not preserved.

@aronatkins
Copy link
Contributor

aronatkins commented Jul 21, 2023

Confirmed. A simple Shiny application within an renv project creates a bundle that contains the app.R , the .Rprofile, and a manifest.json, but not the source renv.lock. We use the renv.lock during bundling, but it is discarded along the way.

@aronatkins
Copy link
Contributor

Removed by

# Once we've captured the deps, we can remove renv from the bundle
removeRenv(bundleDir)

We can probably preserve the renv.lock file but remove the renv directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants