Open filippomc opened 2 years ago
The max-age parameter from jupyterhub allows us to define a maximum amount of time after which the pod is culled even if not idle: https://github.com/jupyterhub/jupyterhub-idle-culler#command-line-flags.
We can set this value in any jupyterhub deployment easily inside and outside osb. @pgleeson any preference on the time to set?
I think 15 minutes to a few hours should be ok to discourage profitable mining, depending on how much we want to be aggressive. Probably NetPyNE sessions need more time than NWB explorer ones
Think about a way to notify the user the session will expire
The max-age parameter works as expected but there is no feedback to the user until a page refresh: . The only solution would be to add a message to netpyne and nwb explorer applications whenever the server goes down. Another solution would be to warn preemptively during the loading that the server will expire after a given amount of time
for osb deployments without login, to discourage mining