You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat(jupyter-singleuser): Update image and packages for 2025
* feat(jupyterhub): deploy the next image to the testing slot
---------
Co-authored-by: V <[email protected]>
Copy file name to clipboardExpand all lines: images/jupyter-singleuser/README.md
+14
Original file line number
Diff line number
Diff line change
@@ -7,10 +7,24 @@ via JupyterHub.
7
7
8
8
A person with Docker set up locally can build a new version of the image at any time after making changes.
9
9
10
+
This can check for any significant security issues with this build
11
+
```
12
+
pip install safety
13
+
safety scan
14
+
```
15
+
Take the package versions from the build file and document with the PR. Do a cleanup step before you make a final build.
16
+
17
+
```
18
+
docker system prune -a #
19
+
docker build . 2>&1 | tee build.log
20
+
```
21
+
22
+
10
23
```bash
11
24
docker build -t ghcr.io/cal-itp/data-infra/jupyter-singleuser:[NEW VERSION TAG] .
12
25
```
13
26
27
+
14
28
## Deploying Changes to Production
15
29
16
30
When changes are finalized, a new version number should be specified in [pyproject.toml](./pyproject.toml). When changes to this directory are merged into `main`, [a GitHub Action](../../.github/workflows/build-jupyter-singleuser-image.yml) automatically publishes an updated version of the image. A contributor with proper GHCR permissions can also manually deploy a new version of the image via the CLI:
0 commit comments