Simon Li

OK, I think what you're really asking is "how do I find out what port jupyter-server is running on" rather than anything specific to jupyter-server-proxy, since it also applies to...

Thanks, looks like it was resolved by #708!

Here's a related mybinder discussion: https://github.com/jupyterhub/mybinder.org-deploy/pull/1778

I agree with making groups managed by either JupyterHub or the Authenticator but not both, since it leads to too many conflicts, and the correct resolution will be different for...

I agree, I attempted this but all the tests broke so I decided to leave it for the future.

The original idea behind `allow_all` is to allow any user without having to define allowed users/groups. For example, admins were inadvertently allowing any GitHub user to login to their installations,...

`allowed_scopes` is going to be inconsistent anyway, since all scopes are required, whereas with the other properties you only have to be a member of one. If we wanted to...

`allowed_scopes` or similar is going to be inconsistent anyway, since all scopes are required, whereas with the other properties only one is required.

I don't know..... given this is a new property we could go for the list-of-lists only? It's more complicated for admins but at least it's unambiguous?

I've written a repo2docker extension to use Kaniko: https://github.com/manics/repo2kaniko/ If you use the latest BinderHub that includes https://github.com/jupyterhub/binderhub/pull/1766 and https://github.com/jupyterhub/binderhub/pull/1795 this config should work: ```yaml config: KubernetesBuildExecutor: docker_host: build_image: "quay.io/manics/repo2kaniko:0.1.0"...