shinyapps-package-dependencies VS shinyproxy-hello

https://www.shinyapps.io

Pricing page mentions something about 'active hours', and if you're on 'free' or 'starter' tier, no more users can use the app until next month. Their pricing page doesn't mention anything about 'concurrent' users, but that error message might just be a legacy holdover?

Docker would potentially be an option. Look at https://github.com/rocker-org/rocker-versioned. There is also https://www.shinyapps.io/ if you would rather not host the app locally.

https://www.shinyapps.io is fairly simple to implement. (The actual shiny less so )

Yes. The lowest-effort path is going to be a subscription to shinyapps, which comes with basic authentication and some control over compute/memory allocation.

My experience was that it was unreliable. Bit sluggish, and sometimes the app would not start and I would have to restart computer and hope it would work. But I thought I would mention it as an option since it fit your description. Is there a reason why you cannot deploy it to https://www.shinyapps.io/ ?

R Shiny is the way. https://www.shinyapps.io/

Keep in mind that Shinyapps.io is a managed service and comes with some limitations regarding dependencies: required R packages need to be able to run on Ubuntu Linux and cannot rely on graphical display only (Tcl/Tk). Installing packages from Bioconductor needs the repositories set by setRepositories(). If a package has missing system dependencies, you can find available system packages here, or file an issue here.

The following image gallery shows how to deploy the Hello app to the Shinyapps.io service:

This post is based on the analythium/shinyproxy-hello GitLab project. Readt about the Shiny example and basic docker concepts before continuing. The project contains the demo Shiny app in the app folder: