Hi @fmichielssen,
Using docker-volumes: [ "/host/mnt/${SHINYPROXY_USERNAME}/path1:/container/path1" ]
would definitely help, the only thing is if authentication is disabled, this might cause an error since I guess SHINYPROXY_USERNAME will be evaluated to null. If nicely implemented, this feature looks to me is very useful for user customized app. One thing I’m worried about is that the variables in the application.yml should be the host’s variables, letting SHINYPROXY_USERNAME be available here is a bit confusing since at the same time there might be a few users using shinyproxy.
I don’t quite get the docker-env-file solution because I don’t get a chance to generate an env file containing the logged in user name for each user and point to it in the application.yml file. Sounds more like the shinyproxy app itself should start the docker with some specified env variables or an env file.
Since Shiny apps are client-server applications, I think encoding some of the parameters in the URL will help as well. As said in my last reply, even the env variable is passed to the docker container, the Shiny App process still can’t access it(the container can). It’s like the Shiny Server modified the enviroment variables before launching each App. A suggested way from Shiny google group is to execute ‘env’ command after the container launches and write the results to a file and later refer to the file from within the Shiny App, but I keep failing to use CMD(or ENTRYPOINT) to achieve this in my dockerfile.