GRI-1876: deployment note, one server behind a reverse proxy, many campuses #105
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!105
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/GRI-1876-deployment-note"
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?
Summary
GRI-1876 / signage #28: rewrites
plan/operations/deployment.mdas the realdeployment note the product owner deploys from alone — one server on the
main campus behind his reverse proxy, clients on several campuses over
wss://. Every command was checked against the code indev; most were runfor real on this build host (server booted against a real Postgres,
first-user setup, login, media/URL upload, playlist create/assign, and the
PDF refusal all verified end to end).
Covers, with real config and commands: server install (Compose + systemd,
the actual
config.tomlkeys and their env overrides), the reverse proxy(nginx/Caddy/Traefik, the
WebSocketupgrade headers, and why[enrolment] trusted_proxiesis not optional), first-user setup and login(including the
Secure-cookie-needs-HTTPS gotcha), client rollout (the.deb, pointing it at a server, device admission order), campus IP rules,content (URL works today, PDF does not yet), playlists, and
backup/upgrade/health.
Two real gaps turned up while verifying, handled rather than hidden:
scripts/package-client-deb.shbuilt and shippedrenderer_spike—crates/client/Cargo.toml's own[[bin]]commentalready names
grimoirix-signage-client(the real client) as the binarythe
.debshould install. Now builds and packages the real binary;verified by extracting the rebuilt
.deband running it — it reports itsreal start-up error instead of starting the Phase 0 spike.
packaging/client-deb/control.in's description updated to match.POST /mediarefuses every PDF (unsupported_media_type), blocking thisnote's own "done when". The note documents the URL content path (works
today) and flags PDF as pending #104.
are only wired to a frontend mock today (
USE_MOCK = true). The realroutes are in PR #103
(signage #13, open, by
nyssa). The note gives the direct-SQL path thatworks today, plus the exact REST calls to switch to once #103 lands —
read from that branch's real code, not guessed.
Also fixed a stale claim in
packaging/server/README.md("the server doesnot connect to Postgres yet, forge #9 still open") — #9 closed a while ago.
Test plan
./scripts/local-gates.sh— every gate passed (fmt, clippy, test incl.--doc,cargo deny, frontendcheck+build)..deb; extracted and ranit — reports the real "no server is configured" error.
this host; verified
/health,POST /setup,POST /session,POST /media/url,POST /mediawith a PDF (refused as documented)and a PNG (accepted),
POST /playlists,PUT /playlists/{id}/items.docker compose configrenders the Compose file cleanly (daemonaccess still not available on this host/account — same limitation the
previous version of this doc already noted).
docker compose upend to end — needsdockergroup membershipon this host (flagged to Aetherius previously, still open).