New repo for the Packet Station rebuild (Python 3.12, FastAPI, PostgreSQL 16, React, VisualKit, MFilesKit, Docker Compose on docker-1). Nothing is migrated from the M: install. - CLAUDE.md with the safety rules, README, CHANGELOG, docs (BRIEF, PLAN, SECURITY rewritten for the server with the requirement ID table, DEPLOY, stubs for FEED, POLICY, SCHEMA, GO-LIVE, PAPER-FALLBACK). - packetstation CLI: app, worker (heartbeat stub), migrate, doctor, version, healthcheck. Settings from the environment with secret files. Stack guard (test never points at VISUAL production). Security headers and CSP. Trusted proxy resolved by name. JSON logs with redaction. - Migration runner and 0001_base: settings, append-only audit_events with hash chain, ps_notify, grants for ps_app. - Multi-stage Dockerfile (ODBC Driver 18, PESCO libraries from the Gitea index only), compose base, proxy overlay for npm_default, CI overlay, postgres initdb roles, env examples, NPM proxy host notes, Gitea Actions. - Frontend: Vite, React, TypeScript, the PESCO dark theme ported with self-hosted fonts, placeholder sign-in and home. - Verified on docker-1: image builds, CI stack comes up healthy, doctor database checks pass, 77 server tests pass against PostgreSQL. Co-Authored-By: Claude Fable 5.1 <[email protected]>
1.1 KiB
Packet Station go-live
Status: planned, phase 10. This is a stub. It lists what the approved plan and the brief say this document will contain. See PLAN.md.
Purpose
The go-live procedure, written with Clerical and the shop.
Date and boundary
Pick the date. Set the feed's go-live boundary to it, so work orders released before it stay out of the new system.
People and groups
Spencer and IT add people to the PS-* groups in AD, using the M: install's user list as the guide. Welder stamps and station limits are entered on the Admin page.
Tablets
Register the shop tablets as devices.
Cut-over
Point new work at packetstation.pescoinc.biz. Jobs already open on M: finish there.
Retiring M:
When the last M: packet is filed, retire the old install and keep its folder read-only as an archive.
Production start
The production stack starts with explicit VISUAL_SERVER and VISUAL_DATABASE. That start is Spencer's approval.
Incident notes
Who to call, how to lock accounts, rotate keys and run the integrity check (requirement O4).