Just wanted to share something we’ve been working on as part of a wider Jupyter-based project for a university.
The plugin starts a JupyterHub service to manage the user environments.
The Environments page shows the list of built environments, as well as the ones currently being built:
Just like on Binder, new environments can be added by clicking on the Add New button and providing a URL to the repository. Optional name, memory, and CPU limits can also be set for the environment:
Once ready, the environments can be selected from the JupyterHub spawn page:
This will spawn a new user server using
Overall it’s a little bit similar to a Binder running on a single machine
There is also this TLJH issue to find a way to extend the plugin system and enable these kind of use cases more easily. The idea would be to skip the creation of the default TLJH user environment if another one is provided in a plugin.
If anyone has any input on this that would be very welcome!