Skip to content
Snippets Groups Projects
Commit efca9fd2 authored by Adam Fekete's avatar Adam Fekete
Browse files

Update README.md

parent 9cb9b8d2
No related branches found
No related tags found
1 merge request!1New structure
Pipeline #67594 passed
......@@ -16,7 +16,7 @@ The docker image is suitable for running/testing locally and for deploying it by
### Building the docker image locally
```bash
docker build -t analytics-workshop:latest notebook
docker build -t analytics-workshop:latest .
```
### Testing/Developing the notebooks locally
......@@ -97,21 +97,3 @@ Each commit triggers a build process on GitLab Runner. Besides the latest tag, t
Note: The latest tag can be found on the following page:
https://gitlab.mpcdf.mpg.de/nomad-lab/analytics-workshop/container_registry
# Jupyterhub deployment
This part is based on an excellent tutorial (https://zero-to-jupyterhub.readthedocs.io/en/stable/index.html).
All the default values are available on the following link: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/0.8.0/jupyterhub/values.yaml
## Goals
Features:
- single user requirements (1-4 CPU, 1-2 GB RAM, 1 GB home space)
- custom docker single user image (which contains all the necessary packages)
- reloading the tutorials for each user
## Continuous integration/delivery
Sensitive parameters can be passed as environmental variables. All of these variables can be stored in the settings (More Settings > CI / CD) of GitLab.
In the config file, the keys with empty values are necessary and usually, they are defined as environmental variables and applied by the helm command.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment