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 am running a shiny app in an R project, let's call it the parent app. The project has a renv.lock file but it is not located in the project root. The file's location is defined in the environment variable RENV_PATHS_LOCKFILE, which is set in the .Rprofile of the project, before renv/activate.R is run. So far, so good.
The parent app generates code for another shiny app, let's call this one the daughter app. The daughter app file is placed in a separate directory in within the project. From there the daughter app is deployed while the parent app is running.
This process fails because the lock file is not found. It does work when the lock file is located in the project root (as usual) or when it is copied from the location specified by the env var to the project root before calling deployApp. Note that there is no attempt at creating a lock file - it is not found where expected and an error is raised.
Can this be fixed so that custom location of the lock file is taken into account?
The text was updated successfully, but these errors were encountered:
I am running a
shiny
app in an R project, let's call it the parent app. The project has arenv.lock
file but it is not located in the project root. The file's location is defined in the environment variableRENV_PATHS_LOCKFILE
, which is set in the.Rprofile
of the project, beforerenv/activate.R
is run. So far, so good.The parent app generates code for another
shiny
app, let's call this one the daughter app. The daughter app file is placed in a separate directory in within the project. From there the daughter app is deployed while the parent app is running.This process fails because the lock file is not found. It does work when the lock file is located in the project root (as usual) or when it is copied from the location specified by the env var to the project root before calling
deployApp
. Note that there is no attempt at creating a lock file - it is not found where expected and an error is raised.Can this be fixed so that custom location of the lock file is taken into account?
The text was updated successfully, but these errors were encountered: