Cryptograss:Moods/ops/todo: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
4b done (#382); prose batch left; static-script item added; #385's measured result (via update-page on MediaWiki MCP Server) |
ops todo: magenta#402 review, merge, task page (via update-page on MediaWiki MCP Server) |
||
| Line 6: | Line 6: | ||
note: "Both mergeable; #275's 5 checks green (5 Nov). One maybelle deploy covers both. The key goes in first: without it the endpoint answers 503 and the reporter does nothing." | note: "Both mergeable; #275's 5 checks green (5 Nov). One maybelle deploy covers both. The key goes in first: without it the endpoint answers 503 and the reporter does nothing." | ||
done: true | done: true | ||
- task: "Review magenta#402 (a Jenkins check still red after a round wakes the alarm task in #ops)" | |||
who: re | |||
kind: review | |||
link: https://github.com/cryptograss/magenta/pull/402 | |||
- task: "Merge magenta#402, redeploy maybelle, then verify [[Cryptograss:Emergents/Magent/Tasks/Jenkins red]] (its saved revision is what lets it run)" | |||
who: justin | |||
kind: merge | |||
link: https://github.com/cryptograss/magenta/pull/402 | |||
- task: "Set up outgoing email (SMTP): PickiPedia password resets, and later Jenkins alarms by email (maybelle-config#35)" | - task: "Set up outgoing email (SMTP): PickiPedia password resets, and later Jenkins alarms by email (maybelle-config#35)" | ||
who: justin | who: justin | ||
Revision as of 19:53, 5 November 2026
- ☐
- ☐
- ☐Set up outgoing email (SMTP): PickiPedia password resets, and later Jenkins alarms by email (maybelle-config#35)
- ☐
- ☐Cold start drill, step one: the property mapTarget block 26,400,000, about 54,000 blocks from 26,345,852.
- ☐Provision a fresh Hetzner box for drill 1 (hunter-only rebuild), once re's property map is doneAlso holds the vault master for drill 2's re-seed; thrown away after the drill.
- ☐Decide on dedicated hosting for Memory Lane & Postgres per Cryptograss/Magenta hosting migration (contemplation)
- ☐Verify live endpoint timings on maybelle after the perf deploysRe-run the 02:15Z timings for /api/moods/ and cold room loads; re-stamp Cryptograss/Moods/Loading and prefetch (research).
- ☐
- ☐Remove magent's hand-started test wiki (pickipedia-magent-wiki-1, -db-1); keep pg-magent-test, which the test suite usesStill up on 5 Nov. The wiki bind-mounts a path that moved, so it fails on its next restart.
- ☐Leftover -arthel mentions in magenta docs, and the dead justin-arthel in memory-lane's ALLOWED_HOSTS
- ☐Finish emergent-magent: point magenta.sh hunter at a Mood or emergent-magent, then remove the Pi trial's scaffolding (setup_magent_pi, magent_also_harness)
- ☐The emergent rename, prose batch: GeneralOrders, Moods/Instructions, Dials, Wake and the rest still say agentThe code step (4b) is done: magenta#382 merged 4 Nov 00:59Z. One batch, so Justin verifies once.
- ☐Moods page script out to a static file with a hash in its name, so a reload after a deploy that didn't touch it is cached (684 KB inline today)Item 2 of the low-hanging fruit (4 Nov). Item 1, magenta#385, merged and deployed: /api/servers/ went from 0.6–1.4 s to 18 ms (Server-Timing, block 26,350,822).
- ☐Realtime Activity Bar Option A (state-flag registry with heartbeat TTL)
Done (1)
- ☑Jenkins alarms in #ops: add memory_lane_alarm_key to the vault, merge magenta#373, then maybelle-config#275, redeploy maybelleBoth mergeable; #275's 5 checks green (5 Nov). One maybelle deploy covers both. The key goes in first: without it the endpoint answers 503 and the reporter does nothing.