DevelopmentDevelopment Preview
Build from source
What you need#
| Need | Detail |
|---|---|
| Machine | Linux x86_64, 4 vCPU, 16 GiB RAM, 60 GiB free disk. Ubuntu 24.04 is the reference. |
| Docker | Docker Engine with Compose v2, used without sudo and not as root. |
| Other tools | GNU make, git 2.44 or newer, Python 3. |
| Network | The first build pulls pinned base images and dependency caches. |
git clone https://github.com/Svavyom/svavyom.git
cd svavyomBuild and test#
Everything is built and tested inside a pinned, unprivileged Docker toolchain, so the machine needs no Go, Node or Python toolchain of its own.
| Command | What it does |
|---|---|
make docker-public-check | Every gate a public checkout can run (about 7 min) |
make docker-fe-browser | The Chromium tier against the real API process and a simulated host, accessibility included (about 5 min) |
make docker-release | Build the release artifact (about 2 min) |
The release artifact#
It builds the Go binaries and the web bundle, assembles release-out/svavyom-<version>/ from tracked files only, writes MANIFEST.json and SHA256SUMS, and verifies the result. It signs and publishes nothing.
release-out/svavyom-<version>/bin/svavyom-ctl verify-artifact release-out/svavyom-<version>Honest limits#
The build is not yet proven reproducible byte for byte, no hosted CI has run it, and the artifact is unsigned. Real-KVM qualification is a separate, manual, privileged tier on a disposable authorised host and never runs in a gate.