Setting the config file location

[tphelan]

We are deploying a shiny app to a remote container with no write access to /etc. Is there a way to set configurations without putting them in /etc/shiny-server/shiny.conf? Specifically the disable_protocols setting?

Thanks!

[cole]

It looks to me like the first parameter passed to the shiny-server binary is interpreted as the config file. /etc/shiny-server/shiny-server.conf is just the default.

$ /opt/shiny-server/bin/shiny-server /home/cole/shiny-server.conf
[2018-12-11 17:04:29.302] [INFO] shiny-server - Shiny Server (Commercial) v1.5.1.760 (Node.js v6.9.1)
[2018-12-11 17:04:29.305] [INFO] shiny-server - Using config file "/home/cole/shiny-server.conf"
[2018-12-11 17:04:29.347] [ERROR] shiny-server - Error loading config: File "/home/cole/shiny-server.conf" does not exist

[tphelan]

Nice, thank you Cole!

[cole]

My pleasure and glad I could help! If that solves your issue, it might be worth "marking as a solution" so that others can see the question is resolved.

FAQ: How do I mark a solution?

If your question has been answered, don't forget to mark the solution! How do I mark a solution? Find the reply you want to mark as the solution and look for the row of small gray icons at the bottom of that reply. Click the one that looks like a box with a checkmark in it: [image] Hovering over the mark solution button shows the label, "Select if this reply solves the problem". If you don't see the mark solution button, try clicking the three dots button ( ••• ) to expand the full set of options. When a solution is chosen, the icon turns green and the hover label changes to: "Unselect if this reply no longer solves the problem". Success! [solution_reply_author] …

[tphelan]

We are only using the shiny package without shiny-server. Can we reset the configuration file without calling the shiny-server binary? Does running the shiny package even use the default global config file at /etc/shiny-server/shiny-server.conf?

[cole]

Oh not at all. shiny-server is designed to host Shiny applications (start them / stop them / scale them / etc.). Shiny itself already listens on a port and is dependent only on R (i.e. not shiny-server at all), so that shiny-server.conf file is never read if you are running Shiny directly.

I.e. with something like R -e "shiny::runApp()"

[tphelan]

Gotcha, I understand better. Thank you!