You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have, perhaps lazily, fallen into the habit of using renv:install(prompt = FALSE) when packaging up shiny apps for deployment. This works great with base renv as it goes through, finds, and installs all packages used in the directory. My reason for doing things this way is due to non-negotiable company anti-virus software, I can't actually use R when renv is active as many package .dlls get flagged. However, to "easily" deploy applications on our shiny server or test w/ Docker, renv makes life easier. So, though I'm quite sure this not best practice, I have to refrain from using renv until development is complete and simply use it as a deployment tool.
Recently, I have seen a VAST difference in Docker build times and shiny server deployment when using options(renv.config.pak.enabled = TRUE) and would like to go in that direction. However, I have noticed that renv:install(prompt = FALSE) fails when pak is enabled on a couple of different levels.
Finding R package dependencies ... Done!
→ Will update 1 package.
→ The package (103.96 kB) is cached.
+ KernSmooth 2.23-22 → 2.23-24
? Do you want to continue (Y/n)
However, if I simply renv::activate(), restart, and then renv::snapshot(), that seems to find and install packages just fine using the prompts hence the issue.
The text was updated successfully, but these errors were encountered:
I have, perhaps lazily, fallen into the habit of using
renv:install(prompt = FALSE)
when packaging up shiny apps for deployment. This works great with baserenv
as it goes through, finds, and installs all packages used in the directory. My reason for doing things this way is due to non-negotiable company anti-virus software, I can't actually use R whenrenv
is active as many package.dll
s get flagged. However, to "easily" deploy applications on our shiny server or test w/ Docker,renv
makes life easier. So, though I'm quite sure this not best practice, I have to refrain from using renv until development is complete and simply use it as a deployment tool.Recently, I have seen a VAST difference in Docker build times and shiny server deployment when using
options(renv.config.pak.enabled = TRUE)
and would like to go in that direction. However, I have noticed thatrenv:install(prompt = FALSE)
fails whenpak
is enabled on a couple of different levels.Firstly, I am prompted whether I want to install
pak
or not. This is not a huge deal but does not agree with theprompt = FALSE
argument.Secondly, and more importantly, I get this error which I presume is just the way
pak
is set up to work:However, if I:
I'm still prompted:
But then things work after I
Y
:After which point I
renv::snapshot()
.However, if I simply
renv::activate()
, restart, and thenrenv::snapshot()
, that seems to find and install packages just fine using the prompts hence the issue.The text was updated successfully, but these errors were encountered: