![]() I've heard of serious shiny devs combing a web app on another language with shiny to handle your type of situation. Lambda - might not want to use this for shiny server due to 15 minute runtime, but might be perfect for the login piece you want to sit it front to redirect You could have the login page be a plumber or shiny app that then redirects to the other shiny app or uses an iframe or other trick.ĮCS or fargate - similar to above, but running on containers (which are running on EC2 servers, you just don't have to manage them) Host shiny server yourself just like you are used to. Here are a few you can look into and decide what sounds best for you.ĮC2 - simple virtual server. ![]() If anyone has any recommendations or could point me towards a tutorial/stack recommendation it would be super helpful. I think given this set up running ShinyProxy instead of shiny server would be the better choice, if im not looking to pay for shiny server? It looks like this a good use for shiny proxy +docker, but im not sure. ![]() I think my use case isn't anything crazy I have currently have 3 unique shiny apps that I want to distribute to three unique users, with the ability to set up a login and then direct the traffic to the relevant shiny app based on the username entered.Ĭurrently, I have a few demos set up using shiny server on an ubuntu ec2 instance using Nginx and authO, but having some trouble "segmenting" the shiny apps so that users only have access to their app. Ive played around with a few option so far, but im not a webdev so im not sure if im going in the right direction. ![]() Im looking for any recommendations on the best direction for hosting in my use case. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |