SvavyomDocs
Development PreviewWebsite ↗
Documentation Development
DevelopmentDevelopment Preview

Build from source

What you need#

NeedDetail
MachineLinux x86_64, 4 vCPU, 16 GiB RAM, 60 GiB free disk. Ubuntu 24.04 is the reference.
DockerDocker Engine with Compose v2, used without sudo and not as root.
Other toolsGNU make, git 2.44 or newer, Python 3.
NetworkThe first build pulls pinned base images and dependency caches.
Clone
git clone https://github.com/Svavyom/svavyom.git
cd svavyom

Build 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.

CommandWhat it does
make docker-public-checkEvery gate a public checkout can run (about 7 min)
make docker-fe-browserThe Chromium tier against the real API process and a simulated host, accessibility included (about 5 min)
make docker-releaseBuild 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.

Verify
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.

Search the documentation

↑ ↓ to navigate · Enter to open · Esc to close

Type to search the public documentation.