-
Notifications
You must be signed in to change notification settings - Fork 83
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
rsconnect.packrat does not apply to push-button deployment #935
Comments
@kevinushey What's our best option to have a setting from the R console apply in the R deployment session? Is an environment variable more likely to work than an R option? Are only certain options / environment variables propagated? |
Environment variables would be the most reliable, since those should be propagated automatically -- AFAIK we don't try to propagate any specific options (except maybe repos). |
Environment variables are visible in the RStudio IDE R session used for push-button deployment. Not all R options are mirrored into that session. These settings indicate that packrat should be used, even in the presence of an renv.lock. When using packrat, the renv directory and renv.lock file are removed from the bundle directory, as would happen prior to rsconnect 1.0.0. Fixes #935 Fixes #936
* prefer RSCONNECT_PACKRAT over rsconnect.packrat Environment variables are visible in the RStudio IDE R session used for push-button deployment. Not all R options are mirrored into that session. These settings indicate that packrat should be used, even in the presence of an renv.lock. When using packrat, the renv directory and renv.lock file are removed from the bundle directory, as would happen prior to rsconnect 1.0.0. Fixes #935 Fixes #936 * spelling * trailing whitespace lint * feedback
Note: |
From a project that does not use renv (a very simple Shiny application will suffice):
Deploy the project using push-button deployment. The "Deploy" pane will show:
Deploying the same project using the console:
we see the output:
It appears that not all R options make their way to the deploy R session.
The text was updated successfully, but these errors were encountered: