Thanks for the explanation Eric, this makes sense. The first of the two future cases sounds quite appealing.
In our case, the user wants to share his Shiny apps with others. This should work if he makes his app world readable and gives the path to the app’s directory - which the other user enters in the web interface.
Though, he also wants external people to run the app, which is something that they won’t be able to do in OOD, so, he may have to resort (pay for) a VM that we can set up for him, and where they can control their users themselves (the VM would be fairly detached from the rest of our infrastructure so their external users could not access our fileservers, …).
I was thinking that the OpenResty/NGINX will somehow allow external users to access a running Shiny app, if the internal user who runs the app gives them the authentication pieces, but, that would essentially give non-users access to our clusters which I am sure no admin here would like.