Michael, hello.
On 1 Sep 2020, at 18:20, 'Michael Milligan' via Project Jupyter wrote:
> I'm not aware of a "nologin" type solution, but it sounds simple
> enough
> that someone has probably implemented one.
It does sound quite simple. Having created a mildly customised spawner
before, I imagine I could hack up something like this myself, but...
must resist... must resist...
> Unfortunately the weak link here is communicating with users who are
> already in running sessions. Jupyterhub can't easily help there, as by
> that
> time the user experience is under the control of the notebook server,
> jupyterlab, or whatever frontend they happen to be using. So your
> solution
> will depend on what your users are actually doing. I'd also be curious
> to
> know if others in this forum have solutions for that.
Right, I see. I could imagine there being some sort of hook in there
which we could use, but if control is handed over to the notebook
server, I can appreciate that would be hard.
So maybe this is more of a jupyterlab question, than a jupyterhub one.
Best wishes,
Norman