Cryptograss:Moods/emergence/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
maybelle deployed, Blue Railroad done; add the cron-health fix (#183) (via update-page on MediaWiki MCP Server) |
m Merged, says GitHub: https://github.com/cryptograss/maybelle-config/pull/183 |
||
| Line 7: | Line 7: | ||
link: "https://github.com/cryptograss/maybelle-config/pull/183" | link: "https://github.com/cryptograss/maybelle-config/pull/183" | ||
note: "cron-health has not compiled since 2026-09-04: none of its checks (backups, audit, rsync, podcast import) have run for five weeks. Look at the first run after the deploy; it may show real staleness that was hidden." | note: "cron-health has not compiled since 2026-09-04: none of its checks (backups, audit, rsync, podcast import) have run for five weeks. Look at the first run after the deploy; it may show real staleness that was hidden." | ||
done: true | |||
- task: "Revoke old GitHub tokens nothing uses any more" | - task: "Revoke old GitHub tokens nothing uses any more" | ||
who: justin | who: justin | ||
Revision as of 19:04, 10 October 2026
What people in the magent-self Mood have been left to do. Kept by magent; anyone may tick an item.
- ☐Revoke old GitHub tokens nothing uses any moreDeploys use one token, magent_github_token, which was not among the leaked values. On jMyles and magent-cryptograss, revoke any token not used recently.
- ☐Say whether the 2025 Porcupine stub secrets were ever registered on a deployed claim contractThe leaked value came from a local dev build on 2025-06-11 (token 1). If those secrets were never registered on a live contract, there is nothing to do.
- ☐Delete the pre-redaction dump on hunter once cron-health shows the memory-lane backup stage greenIt still holds the secrets redacted on 2026-10-04.
- ☐
Done (6)
- ☑Merge maybelle-config#183 and deploy maybelle, so cron-health compiles againcron-health has not compiled since 2026-09-04: none of its checks (backups, audit, rsync, podcast import) have run for five weeks. Look at the first run after the deploy; it may show real staleness that was hidden.
- ☑Deploy maybelle after the database password rotation
- ☑Rotate the Blue Railroad bot password
- ☑Rotate the PickiPedia database passwordTook the wiki down 18:17–18:48Z. Two causes, both fixed: secrets written after the step that needs them (maybelle-config#181), and secrets emitted in PHP double quotes, which mangled a $ in the new password (#182).
- ☑Rotate the delivery-kid key and the wiki's $wgSecretKey
- ☑Rotate Alchemy, Jenkins admin, memory-lane SECRET_KEY, code-server, GlitchTip admin