-
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 profile options ignored #542
Comments
Using the 0.8.24 CRAN release of this package and # saved as $HOME/.rsconnect_profile
cat("ATTENTION: This is the HOME/.rsconnect_profile\n") # saved as PROJECT/.rsconnect_profile
cat("ATTENTION: This is the PROJECT/.rsconnect_profile\n")
options(rsconnect.max.bundle.size = 10) A call to the rsconnect::deployApp(server = "SERVER-NAME", account = "ACCOUNT-NAME")
#> ATTENTION: This is the HOME/.rsconnect_profile
#> ATTENTION: This is the PROJECT/.rsconnect_profile
#> Error in bundleFiles(appDir): The directory /Users/aron/dev/rstudio/standalone/shiny-rsconnect-site cannot be deployed because it is too large (the maximum size is 10 bytes). Remove some files or adjust the rsconnect.max.bundle.size option. The bundle size is not enforced, however, when specifying an enumerated set of files; this is the path often used by the RStudio IDE when deploying content. rsconnect::deployApp(server = "rsc.radixu.com", account = "aron", appFiles=c("app.R"))
#> ATTENTION: This is the HOME/.rsconnect_profile
#> ATTENTION: This is the PROJECT/.rsconnect_profile
#> ... deployment succeeds ... The same behavior is seen with rsconnect-0.8.16. |
Paths that use |
The |
@JsizzleR - Could you give more details about your session? How were you deploying? Did you set other rsconnect options? |
@aronatkins in |
@hadley - more logging feels right, yes. Should the |
@aronatkins yeah, it should. And I don't think changing it to the correct default should affect existing code, since this all needs to be "side-effect"y code anyway. |
When using rsconnect version 0.8.24, the settings in these files aren't taking effect:
The two settings used were:
Downgrading to the previous version used, 0.8.16, resolved the issue.
The text was updated successfully, but these errors were encountered: