- HTML 47.3%
- Dockerfile 31.1%
- Shell 21.6%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Ionori builds its MLS library (openmls) with cargo and wasm-pack; the runner had no cc to link with. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
| .forgejo | ||
| authentik | ||
| bookstack | ||
| debian-runner | ||
| docker-runner | ||
| dotnet-runner | ||
| erpnext-v15 | ||
| erpnext-v16 | ||
| test | ||
| LICENSE | ||
| README.md | ||
containerimages
The images Talaryon builds itself, published to code.talaryon.dev/talaryonlabs/<folder>. Every folder is one image, of
one of two kinds:
- Dockerfile - the image's version is the Dockerfile's
ARG IMAGE_VERSION=...(its first line after the comment). Use it in the Dockerfile wherever the version goes (FROM ...:${IMAGE_VERSION},git checkout ${IMAGE_VERSION}), so the tag and what is built can't drift apart. - ERPNext recipe (
erpnext-v15,erpnext-v16) - no Dockerfile of its own, built with frappe_docker and published to the one imageerpnext, the version being the major of the erpnext release (erpnext:v16-<revision>):apps.json- the Frappe apps, each pinned to a tag;frappe.env-FRAPPE_DOCKER_REF(the frappe_docker commit),CONTAINERFILE(images/layered/Containerfileorimages/custom/Containerfile), and every other line a build argument (FRAPPE_BRANCH,PYTHON_VERSION, ...).
There are no VERSION files: to update an image, change its IMAGE_VERSION (or the pins in apps.json) and commit.
Tags
Each build is tagged
| Tag | |
|---|---|
<version>-<revision> |
exact, never moves - e.g. bookstack:v26.03.3-77. The revision is the number of commits that touched the folder (git rev-list --count HEAD -- <folder>): it only grows, and every change to an image is a new tag. |
<version> |
the newest build of that version |
main, latest |
the newest build - not for erpnext, whose v15 and v16 are both current |
and labelled org.opencontainers.image.version=<version>-<revision>, which StackEngine reads as the image's version.
Building
.forgejo/workflows/build-images.yaml builds, on a push to main, every folder the push changed (all of them when
.forgejo/ changed), each in its own job; run it by hand to build the folders named in images (or all of them).
A tag the registry has already isn't built again.
Locally:
.forgejo/build-image.sh bookstack --plan # the exact tag it would get
.forgejo/build-image.sh bookstack # build it here
.forgejo/build-image.sh bookstack --push # build and push (REGISTRY=..., default code.talaryon.dev/talaryonlabs)
A new image is a new folder with a Dockerfile (or apps.json + frappe.env) - nothing else to set up.