Hello, fellow technical colleagues~
I’d like to consult a technical issue regarding container management with ShinyProxy.
We currently face two scenarios:
Short-term tasks: Some applications have a short runtime and are fully managed by ShinyProxy for their lifecycle — when users close the browser, the Docker container is automatically triggered to shut down. (This works perfectly with ShinyProxy.)
Long-term tasks: Other applications involve extremely time-consuming computations. Users may close the browser before the task completes (to avoid waiting), but the container needs to keep running until the computation finishes, then shut down automatically.
Could you please advise on implementing the following requirements:
Differentiate between task types and customize a strategy for long-term tasks to “maintain container operation after browser closure”.
Automatically trigger container shutdown after the computation completes.
Thank you.