> Spawner almost seems like a more general purpose JupyterHub
That's actually a very good way of putting it to people who understand the reference!
One of the things I've been playing with is actually using Spawner to spin up Jupyter Lab notebooks with their new(ish) collaboration feature. Jupyter and VS Code both work very nicely with Spawner's architecture out-of-the-box, since they can be put into a container and accessed entirely through an HTTPS connection.
Yeah a 'spawn a VS code server instance on these files' microservice could be super handy for lots of things. There are fantastic technical doc tools like mkdocs, mdbook, etc. but none of them have an editing interface. You could add an 'edit' button to their generated HTML that opens a spawned VS code server instance on the files, and now you've got a little wiki / knowledge base that a small team can work from.
That's actually a very good way of putting it to people who understand the reference!
One of the things I've been playing with is actually using Spawner to spin up Jupyter Lab notebooks with their new(ish) collaboration feature. Jupyter and VS Code both work very nicely with Spawner's architecture out-of-the-box, since they can be put into a container and accessed entirely through an HTTPS connection.