Files

RogueWave a294a8a9fb chore(status): mark Phase 0 complete; add deploy-status.sh

Server provisioning ran successfully: nginx + PostgreSQL + Redis live, UFW
active (22/2222/80/443), TLS issued for feedthepyre.com (+www), pm2-pyre
service enabled. Status dashboard updated (Phase 0 done; infra all green).
Adds scripts/deploy-status.sh for friction-free status-page redeploys.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-05-31 02:48:38 +00:00

index.html

chore(status): mark Phase 0 complete; add deploy-status.sh

2026-05-31 02:48:38 +00:00

README.md

feat(infra): Phase 0 provisioning + dev status dashboard

2026-05-31 02:34:13 +00:00

status.json

chore(status): mark Phase 0 complete; add deploy-status.sh

2026-05-31 02:48:38 +00:00

README.md

PYRE Status Dashboard

A static, self-contained dark "ember"-themed page the team uses to track PYRE MVP progress. It is a snapshot, not live telemetry.

Files

status.json — the single source of truth. All content on the page (phases, checklists, infra, dates, links) comes from here.
index.html — the prebuilt rendered page. Committed so the page works even before anyone runs the generator. Self-contained: inline CSS, no external requests, no JS.
README.md — this file.

Editing & regenerating

Edit status.json — flip an item's "done" to true, update a phase "state" (todo / in_progress / done), or bump "updated".
Regenerate the page from the repo root:
```
node scripts/gen-status.mjs
```
The generator is dependency-free (plain Node ESM, no npm install). It reads infra/status/status.json and rewrites infra/status/index.html, recomputing the overall % complete from the item done-counts. It prints the output path when finished.
Commit the regenerated index.html alongside the status.json change so the prebuilt page stays consistent with the data.

Deployment

The provision script deploys infra/status/* to /var/www/feedthepyre/status, and nginx serves it as the site root (feedthepyre.com) until the real PYRE app ships. Because index.html is prebuilt and self-contained, deployment is a plain file copy — no build step or generator run is required on the server.