Proxying services on a named docker-compose network

[jupyterhub]

Proxying services on a named docker-compose network

[manics]

Technically it should be easy, just make the host configurable:

jupyter-server-proxy/jupyter_server_proxy/handlers.py

Line 153 in 8f0799d

host='localhost',

, and it would also be easy to not start the process.

However that allows someone to configure jupyter-server-proxy to behave as a general proxy, i.e. it can proxy any internal host and service. You could do that anyway since you can do anything in Python, but should it be supported by jupyter-server-proxy?

[psychemedia]

@manics I have started looking at various ways of using Jupyter notebook auth and jupyter server proxy as a way of providing auth to other apps. It's often easier to link in other apps as other docker images. Adding nginx as the proxy is one way to handle it, but that makes it more complex for the user.

I realise I am probably an outlier but the vision I work to is someone who isn't a sysadmin but who may want to pull workbenches together comprising several apps; to a certain extent, docker-compose makes that tractable.

Setting up nginx is one more thing to have to know about (and if I'm a researcher in an NGO or a freelance or local press data journalist, that's an overhead I'd rather not worry about): much easier to just use the notebook server as my proxy?