Hello,
I’ve noticed that each time I click the launch button in Binderhub, a new Kubernetes Pod is created in the cluster.
Is it possible to reuse an existing environment if it’s already running instead of creating a new one each time? Any insights on whether this can be configured?
The default configuration of BinderHub uses anonymous users (no login required), so there’s no way to identify a user, and no way to get back to a server unless you know it’s url (and token). If you turn on authentication a user will be taken to their existing server:
I actually have authentication enabled in my configuration but I am still seeing that environments are created always so I constantly have to clean the named servers.
It is worth mentioning that I have installed Binder in an existing Jupyterhub environment.
I don’t think the current BinderHub adequately handles your requirement since it only integrates with JupyterHub via a spawner.
If you’ve got time to do some investigation or development it might be worth looking at
You could then write your own JupyterHub integration, e.g. to launch a named server named after the repo name, providing a consistent link.
Thank you, I will take a look at Binderhub Service