Backend installation and requirements
The backend builds thirteen executables from one independently versioned Go module. Its Compose deployment is the supplied development installation path. There is no fully supported turnkey production installer or declared production capacity tier in this baseline.
Build from source
The module selects go1.25.13; Go can download the requested toolchain when configured to do so. Native builds and private module access require the usual compiler/module network availability. Docker builds select their own builder image.
make verify
make build
make images
make build writes component binaries under dist. make images builds each component image using deploy/Dockerfile; its final stage is a non-root scratch image. See CI for the checks each release candidate receives.
Local installation
Follow the quickstart. Development CA, server, agent, and caller material is generated under .local/pki. This is a deliberately local trust domain. Do not reuse its private material across production estates.
Persistent broker and database volumes outlive stopped containers. make down is an explicit destructive reset. Before changing existing data, inspect migration ownership.
Production prerequisites
A production deployment must supply independently managed certificate authorities, private-key access controls, authenticated/encrypted broker and database connections, appropriate topic replication, per-process credentials, storage/retention sizing, and a tested recovery procedure. The repository offers configuration mechanisms for several of these, not a completed production topology.
Do not derive platform requirements from the documentation site's small static-server footprint. Backend advisory imports and analytical storage have independent workload and capacity needs. Refer to production readiness and the measured performance baseline.
Source evidence
Reviewed against the source baseline. Seagull-backend-v2/go.mod · Seagull-backend-v2/Makefile · Seagull-backend-v2/deploy/Dockerfile · Seagull-backend-v2/deploy/compose.yaml.