Container images for the ZetaOSS MediaWiki development environment.
ghcr.io/zetaoss/zbase: MediaWiki runtime and extensionsghcr.io/zetaoss/zdev: development tools based on a releasedzbase; the zengine Git workspace is mounted at runtime and is not part of the image
The images have independent versions in the root versions.env file. zdev
uses the exact ZBASE_VERSION declared in that file.
The root Makefile reads versions.env and builds zbase before zdev.
# Build the declared zbase version and then build zdev from it.
make
# Build only one image.
make zbase
make zdev
Running make zdev by itself uses the ghcr.io/zetaoss/zbase version declared
in versions.env. Running make first builds that base locally before building
the dependent image.
Update versions.env and merge the change into main:
ZBASE_VERSION=0.2.0
ZDEV_VERSION=0.5.0GitHub Actions checks whether the corresponding zbase/v0.2.0 and
zdev/v0.5.0 Git tags exist. Missing versions are built in zbase → zdev order,
published, and then tagged automatically. Each image receives the full
version, minor version, latest, and an immutable commit tag:
ghcr.io/zetaoss/zdev:0.5.0
ghcr.io/zetaoss/zdev:0.5
ghcr.io/zetaoss/zdev:latest
ghcr.io/zetaoss/zdev:sha-<commit>
If a Dockerfile changes after its current release without the corresponding version bump, the release workflow fails. A new zbase also requires a new zdev version because changing the selected zbase version changes the resulting zdev image.