When you specify a minimum number of containers to be ready for use with the minimum-seats-available parameter, is there any logic to which container will be allocated to a user first?
We have an app which has a long startup time. Sometimes, the first person gets in fine but the second person to log in has a long wait before the container is ready. I’m guessing that they’re being allocated the newly-created container instead of one of the older ones. Could this be the case?
Ideally, a user should always be given the oldest container.
Hi, currently there is no way to control the assignment to a container. The seats are added to a pool, but in no specific order.
You mention a long wait before the container is ready., do these users see the ShinyProxy loading screen or a loading screen of the app (or simply a white page)?
If they see the ShinyProxy loading screen, this means that a seat is not immediately available for the user, either because there are not enough containers or because a container is still starting up. In this case, I guess you have to increase the minimum-seats-available.
In the other case, where the app still has to load/boostrap, this is the expected behavior and some user will always have to for this bootstrap. The best solution here is to inspect your Shiny app and make sure everything is loaded/prepared on startup.