jupyter-simple/entrypoint.sh

#!/bin/sh -x
VENVDIR=/v
DATADIR=/data
JUPYDIR=/root/.jupyter

JUPYDEF=/.default.py
JUPYCNF=$JUPYDIR/jupyter_lab_config.py
JUREQFL=$DATADIR/requirements

cd $DATADIR
. $VENVDIR/bin/activate

[ ! -f $JUPYCNF ] && cp $JUPYDEF $JUPYCNF
[ -f $JUREQFL ] && pip install -Ur $JUREQFL

jupyter lab build

( $@ )
initial commit Adds the Dockerfile, entrypoint and default config. 2022-08-17 13:53:57 +01:00			`#!/bin/sh -x`
			`VENVDIR=/v`
			`DATADIR=/data`
			`JUPYDIR=/root/.jupyter`

			`JUPYDEF=/.default.py`
			`JUPYCNF=$JUPYDIR/jupyter_lab_config.py`
entrypoint: Auto-install requirements if any If /data/requirements exists, install all requirements listed in it before starting any commands 2022-08-17 16:23:26 +01:00			`JUREQFL=$DATADIR/requirements`
initial commit Adds the Dockerfile, entrypoint and default config. 2022-08-17 13:53:57 +01:00
			`cd $DATADIR`
			`. $VENVDIR/bin/activate`

			`[ ! -f $JUPYCNF ] && cp $JUPYDEF $JUPYCNF`
entrypoint: Auto-install requirements if any If /data/requirements exists, install all requirements listed in it before starting any commands 2022-08-17 16:23:26 +01:00			`[ -f $JUREQFL ] && pip install -Ur $JUREQFL`
initial commit Adds the Dockerfile, entrypoint and default config. 2022-08-17 13:53:57 +01:00
entrypoint: Build before starting Because /v/share/jupyter/lab is now a volume, there is the potential that it will be empty or out-of-date. We should always kick off a build before starting jupyter-lab. 2022-08-17 16:44:14 +01:00			`jupyter lab build`

initial commit Adds the Dockerfile, entrypoint and default config. 2022-08-17 13:53:57 +01:00			`( $@ )`