Commit Graph

4 Commits

Author SHA1 Message Date
vh b637947ffd docs(park): record the API-key ruling — leave it as is
Operator ruled 2026-08-18 on the 5-character PARK_API_KEY flagged during
the v1.0.0-beta.2 deploy: leave it. The henge is LAN/WG-internal and
never internet-exposed. Written down so the next audit does not re-raise
a question that has already been answered.
2026-08-18 05:49:10 -07:00
vh ec1c482bd5 deploy(park): stonehenge-park v1.0.0-beta.2 on ana-docker
Operator-directed request from park-dev. Rebuilt from tag v1.0.0-beta.2
(commit 2c258f7) and redeployed; park-data volume preserved (28 items,
9 comments verified present after the recreate).

Build source is now exported per-tag to
~/deploy-src/stonehenge-park-v1.0.0-beta.2 rather than overwriting the
single mirror, so the previous tag's tree stays on the host as a
rollback. The mirror was never a git checkout, so the source comes from
`git archive <tag>` against a box that has the repo -- which also leaves
park-dev's working tree untouched.

Verification, and two things worth writing down:

- HEAD 401s on EVERY route, including /healthz and /. So park-dev's
  suggested check `curl -sI .../ui/assets/favicon.svg` reports a false
  failure. GET is 200 with content-type image/svg+xml; the packaging is
  fine and all nine assets are in the wheel. App-wide and pre-existing,
  not a beta.2 regression -- /healthz predates this release.

- /park/due-count returning 0 is not a data-loss signal; it counts what
  is due now, and /park/due is empty across overdue/today/stale. Items
  survived: GET /park returns all 28. README now says to check that
  instead of the due counters.

Also corrected the stack README, which still told the reader to build on
nh3-docker and verify against 10.100.50.40 -- the host decommissioned for
this stack on 2026-08-13 and the one park-dev explicitly asked us not to
deploy to.
2026-08-17 22:21:09 -07:00
vh f6acb90d00 park(migration): promote the henge to permanent home on ana-docker
Operator-directed (Vuong 2026-08-13): migrated stonehenge-park off the nh3-docker
beta deployment to a permanent fixture on ana-docker (10.250.50.70) before the
v1.0.0 final cut. SQLite (park-data) migrated consistently (stop -> tar-copy ->
start; byte-identical). restic auto-covered by ana-docker's /var/lib/docker/volumes
source. Stable name park.phasefinal.com -> 10.250.50.70 (Cloudflare DNS-only) so
clients decouple from the host IP. Homepage tile 'The Henge' added. nh3-docker stack
left stopped as rollback pending park-dev cutover verification.
2026-08-13 14:28:42 -07:00
vh 0dcce02e47 stacks(park): mirror stonehenge-park v1.0.0-beta.1 deploy on nh3-docker
New self-contained stack (FastAPI + SQLite + in-process scheduler) from
vh/stonehenge-park tag v1.0.0-beta.1, deployed to nh3-docker per park-dev's
operator-approved request. Port 8420, LAN/WG-internal; park-data volume (SQLite
sole source of truth) covered by the host's /var/lib/docker/volumes restic source.
Image built locally (no registry yet); .env carries PARK_API_KEY from the vault.
althing push to henge-crow deferred (PARK_ALTHING_CHANNEL empty) until althing-cli
is wired into the container.
2026-08-12 18:48:22 -07:00