Maxim Nazarov

this should have been fixed in https://github.com/r-hub/sysreqs.app/pull/8, but it seems that the page was not re-generated...

seems to be because https://s3.amazonaws.com/clippy.js/Agents/ is not working anymore - see https://github.com/pi0/clippyjs/issues/10 for potential solutions, e.g. replacing clippy.BASE_PATH with https://cdn.jsdelivr.net/gh/pi0/clippyjs/assets/agents/ should work, but even better maybe to host the necessary...

Forward slash is not currently supported since apps may have sub-paths inside, and then it would be difficult to distinguish if by going to `/test/app` you want to access the...

Hello, Please try the suggestions mentioned in https://support.openanalytics.eu/t/container-volumes-question/1018/3 and https://support.openanalytics.eu/t/shinyproxy-in-container-mounting-volumes-on-windows/1205

I think it is a matter of finding how the volumes need to be defined on docker compose for windows, and not a shinyproxy issue per se. Unfortunately, I don't...

also you can configure the log to be stored in a volume-mapped folder, so that it persists on the host for you to check later.

Not really an advice, but a question - why do you start the app from the terminal and not from the console?.. the latter should work fine. And the former...

Do you have `DISABLE_AUTH: true` in the `container-env` as described in [README](https://github.com/openanalytics/shinyproxy-rstudio-ide-demo#shinyproxy-configuration)? Normally it shouldn't redirect to /auth-sign-in in this case.

ok, but the above WWW_ROOT_PATH seems to be correct... Which rstudio image do you use? Is it the one from this repository or some custom one?

> “Warning: Error in library: there is no package called ‘aws.s3’”. This suggests there could have been errors during the package installation, so you should check the logs of the...