Yuvi

Yeah, I think to begin with asking users to put os.getenv is probably the way to go. I think @ryanlovett added most of the websocket stuff, so might have more...

Thank you for opening this, @sudhaker! Does the 'timeout' option (documented under https://jupyter-server-proxy.readthedocs.io/en/latest/server-process.html#server-process-options) work for your use case? It defaults to 5 but can be increased.

@manics I think you're right! The rest of the stuff can happen post 1.0 but pre-blog post.

I've now published 1.0! Thanks for the push, @manics! I've opened #100 for merging rstudio back in here.

https://github.com/jupyterhub/jupyter-server-proxy/pull/101 for documentation on 'convenience' packages (new name for 'contrib' packages)

> Counterpoint to myself: if we can run BinderHub with just docker, it will make local testing of most of the logic _way_ easier, maybe _improving_ maintenance of the whole...

@manics has made amazing progress on this, and it's possible :) I think there are a few more things we need to clean up. - [ ] Make our Quota...

Just wanted to bump this to see where this is :) There's a merge conflict already, would be great to get this in before there are too many of those!...

To perform some thread necromancy, I think forcing SSL on a per-server basis would mean we don't have to mangle URLs, right? I want folks to be able to use...

There's also the option of passing JSON as a 'resourceRequests' parameter.