Describe the bug
When users want to use an application there are 2 different options:
opening the terminal and launch a machine manually
opening a application which is starting a t1 automatically
In configuration 1., I can use my application without limits as long as I don't close the SEPAL window. If I use configuration 2. and I stop interacting with the dashboard, after 5 min my instance shutdown and my application stop running.
It is preventing people to discuss application results on the fly which is a problem when we are streming result on a map before exporting.
My guess is that the terminal continue to interact with the instance continuously whereas Jupyter is rendered so it send Python request only if you click on something. Would it be possible to prevent the instances to die when an application is running ? either or not it is executing stuff ?
Describe the bug When users want to use an application there are 2 different options:
In configuration
1., I can use my application without limits as long as I don't close the SEPAL window. If I use configuration2.and I stop interacting with the dashboard, after 5 min my instance shutdown and my application stop running.It is preventing people to discuss application results on the fly which is a problem when we are streming result on a map before exporting.
My guess is that the terminal continue to interact with the instance continuously whereas Jupyter is rendered so it send Python request only if you click on something. Would it be possible to prevent the instances to die when an application is running ? either or not it is executing stuff ?