ENH: Makefile for development

[sjsrey]

The current README instructions has the docker container not returning a shell for entry but rather the lab is running. It isn't clear how to move onto the build steps from that point.

The Makefile here is intended to support either running the lab in the container w/o a shell, or getting as shell.

[darribas]

Hey! Thanks for this. My approach has been to launch JupyterLab on a container and then run all the commands to build the website, etc. from inside JupyterLab (on a terminal window, which is equivalent to launching the container with start.sh, but lets you also edit files and try notebooks out). My thinking in that is that if someone is not using a container but has all the dependencies installed locally, they should be able to replicate it too and it doesn't lock them on using Docker.

But it is true that this could be better documented, would it make sense to try to expand on this a bit in the README.md?

[darribas]

the official Jupyter stacks have a convenience script that drops you into a terminal by calling start.sh:

docker run -it --rm  -p 8888:8888 -p 4000:4000 -v ${PWD}:/home/jovyan/work darribas/gds_dev:4.0 start.sh