Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/manics/jupyterhub-container-images
https://github.com/manics/jupyterhub-container-images
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/manics/jupyterhub-container-images
- Owner: manics
- License: bsd-3-clause
- Created: 2024-11-24T23:17:24.000Z (about 1 month ago)
- Default Branch: main
- Last Pushed: 2024-11-24T23:57:10.000Z (about 1 month ago)
- Last Synced: 2024-11-25T00:23:55.375Z (about 1 month ago)
- Language: Dockerfile
- Size: 7.81 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# JupyterHub Container Images
[![Build](https://github.com/manics/jupyterhub-container-images/actions/workflows/build.yml/badge.svg)](https://github.com/manics/jupyterhub-container-images/actions/workflows/build.yml)Definitions and workflows for publishing JupyterHub container images.
## How this works
All pushes to `main` (and any designated backport branches) are built and published.
Pushes to `main` are assumed to always be the latest, so images are always tagged with- `MAJOR.MINOR.PATCH-BUILDNUMBER`
- `MAJOR.MINOR.PATCH`
- `MAJOR.MINOR`
- `MAJOR`
- `latest`where `MAJOR.MINOR.PATCH` is the JupyterHub version.
## Publishing backports
Backports are published in their own branches.