I can't see any method to adjust the worker settings for a deployed shiny app on Posit Connect Cloud i.e. those found at Settings > Advanced on shinyapps.io like the Connection Timeout. Am I missing something or are these not available?
Oh now I see Increasing the time-out settings for my R-Shiny app hosted on Posit Connect Cloud - #3 by danhillary and the answer is no. That's quite annoying.
Hi Simon,
The team is currently working on exposing these settings to all users, and we anticipate it will hit the platform in about a month. I'll let you know when it's ready.
Alex
1 Like
Hi Alex.
That's good to hear. In the meantime I came up with a bodge to keep the app connected 
Cheers
Simon
Looks like it launched! Some great improvements, thank you team! 
2 Likes
@alex_chisholm That looks great, but one more question - is there a plan to increase the available instances? On shinyapps.io we can have up to 5 which is useful when there are lots of users. In an ideal world that could be increased further. For example today I had a query about having 100 concurrent users in a workshop, each which would use ~ 2GB RAM. Currently the only solution is to spin up the multiple instances manually but then you need to manage the URLs carefully.
Hi, @Simon_Smart . Yes, horizontal application scaling is also on the roadmap, but we don't know how soon it will be prioritized. Before that, we will be adding greater compute levels to the Advanced plan.
Out of curiosity, what type of application are these users interacting with?
Good to hear. More power would also be good - it's not easy to find cloud services that can give you loads of resources for a short time, but always be available to users.
It's an app which uses CRAN: Package gemtc to fit Bayesian models which are RAM intensive. The difficulty with workshops is that everyone runs the models at the same time so you get a massive spike in required resources.
@Simon_Smart , is the repo with the application public? If so, perhaps you could have them all create a Connect Cloud account and then deploy it themselves from the repo, getting their own instance to work with.
Ahh yes that's an option I hadn't considered. I'll take a look at how long it takes to deploy to see whether that's a feasible option.
45 seconds! That's really impressive!