psychemedia/jupyter-postgres-demo

Demo of launching a binderhub notebook server with a free running postgres server

jupyter-postgres-demo's Issues

Running postgres in repo2docker / Binderhub containers

postgres likes running under postgres user or root.

The dockerfile-omero rewrites permissions over the /run/postgresql/ directory to allow joyvan to start postgres explicitly.

The sudoers branch gives jovyan elevated sudo privileges so that it can start the postgres service.

The master branch is broken: the postgres server can't be started.

pgadmin - query tool raises Invalid HTTP error

Trying to launch the pgadmin query tool raises the error:

Bad Request

Invalid HTTP Version 'Invalid HTTP Version: 'on testuser@test1?query_url=&server_type=pg HTTP/1.1''

See also this related SO question on pgadmin in docker.

Running pgadmin in Mybinder

Via Jupyter discouse site [thread], h/t @betatim for debug strategy:

With a bit of editing of pgAdmin4.py to get it to log at DEBUG level to the console and starting it from a console I see that it sends 302 redirect to /browser when you first visit it at ../proxy/5050/. This request then ends up with a 404 because of the leading / in the redirect location.

If instead you navigate to .../proxy/5050/browser/ (with trailing slash) there is no 302 redirect and you get to see a bit of HTML produced by pgAdmin. However the JS doesn’t load because the paths all start with a / that make them absolute.

The missing puzzle piece is how to configure pgAdmin4 (a flask app) to understand that it is being served from a URL prefix. I can’t make that work. It is a general problem that I have with flask apps :-/

And @manics for getting pgadmin working (#2).

PgAdmin and server mode

I've been working on setting up a postgres+jupyterlab image, and this repo has been the gift that keeps on giving, so thanks for all the hard work @psychemedia and @manics!

I'm looking at some of the archaeology of your efforts to get pgadmin4 running, and I see that at some point you stopped trying to disable SERVER_MODE. As I'm going through the same contortions right now, I thought I'd ask about it here. Is there a reason you couldn't get SERVER_MODE=False working? I'd like to avoid an additional user login if at all possible. Also, why did you start serving the application with gunicorn rather than its built-in server?

Any insight would be appreciated.