A simple "file management" style app to experiment with serving jupyter notebooks from within a web application.
You will need to create two environment files to run this locally:
.secrets.env
POSTGRES_USER=username
POSTGRES_PASSWORD=password
POSTGRES_HOST=postgres
POSTGRES_PORT=5432
POSTGRES_DB=db_name
SECRET_KEY=flask-secret-key
JUPYTERHUB_SECRET=jupyterhub-secret-key
.env
COMPOSE_PROJECT_NAME=example_name
(yes maybe this could've been checked in and you might not need it)
make build
: Builds the docker containersmake up
: Starts the docker containersmake logs [service=service]
: Attaches to the logger - you can provide the optionalservice
param to connect to a specific servicemake stop
: Stops the docker containersmake down
: Tears down the docker containers - this will delete all of your data.make shell
: Opens shell on the flask server
- This is not at all a finished product - lots does not work yet :) and there's a lot i haven't tested.
- You should log out before running
make down
. The auth management isn't great so the cookies aren't cleared when you runmake down
. - I haven't tested creating subdirectories on jupyter (creating local subdirectories works but I'm not sure if the integration with the jupyter api is right)
- Log in takes a few seconds and there's no progress spinner. The jupyter server is started on login and that takes a bit of time