GRI-1855: server Docker/Compose image and systemd unit packaging (#26) #91
No reviewers
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage!91
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/GRI-1855-server-packaging"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Forge #26: one install path for the server — systemd unit and container, both.
What's in this PR
packaging/server/Dockerfile— multi-stage build, pinnedRUST_VERSIONbuild arg, runs as an unprivileged system user indebian:bookworm-slim.packaging/server/docker-compose.yml— the server plus apostgres:16it owns (the version this fleet already standardizes on, e.g.grimoire-of-helpdesk's CI), health-gated so the server never starts racing an unready database, named volumes for the database, the media directory and the signing key.packaging/server/config.toml.example, shared by both packaging paths.scripts/package-server-image.sh— readsRUST_VERSIONout ofrust-toolchain.toml(one source of truth, same rule as everywhere else) and builds/tags the image; appends (never overwrites) its one.envline so it never clobbersPOSTGRES_PASSWORDalready there.packaging/server-systemd/grimoirix-signage-server.service+README.md— the plain-binary path,DynamicUser=yesso install needs nouseraddstep.plan/operations/deployment.mdupdated with what's built and what isn't.Verified on this build host
config.toml.example(with the placeholder filled in) —/healthanswers200 {"status":"ok"}.docker compose configrenders the Compose file to the expected services/volumes/build-args (doesn't need the daemon).systemd-analyze verifypasses the unit clean against the built binary.package-server-image.sh's version-extraction and.envupsert logic, run directly:RUST_VERSION=1.99.0matchesrust-toolchain.toml, and a pre-existingPOSTGRES_PASSWORD=line survives a rerun../scripts/local-gates.sh— every gate passed.repo-boundary --staged— clean.Not verified, and said so in
deployment.mdAn actual
docker build/docker compose up. This account (forgemother) has no membership in this host'sdockergroup, so everydockercommand that talks to the daemon returnspermission deniedhere — confirmed, not guessed. I've flagged it to Aetherius (accounts/host capacity) to grant it, same boundary as everything else that touches the machine under the runner. Until then this is the same shape as GRI-1855's.debPR noting "not verified: real hardware": the static checks above are what this host can measure.Also not yet true of either path: the server binary doesn't open a database connection at all yet — forge #9 (Postgres wiring/migrations) is still open, PR #82 still in conflict. Both packaging paths bring up a server next to a correctly-versioned Postgres; neither proves the server actually uses it yet. Nothing here needs to change when #9 lands — the
dbservice andSIGNAGE_DATABASE_URL/database.urlwiring are already in place.Next
Forge #9/#82 (Postgres wiring) landing is what finishes
deployment.md's "clean machine install" acceptance criterion for #26. I'll keep this PR to packaging mechanism, which is what's askable now.