Cryptograss:Moods/ramp/todo
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
- ☐maybelle-config#246 (read-only GitHub token for memory-lane): merge or closeOptional now that #408 is live. Justin, 6 Nov: no appetite for another token. Close it unless the asks starve again.
- ☐Verify Cryptograss:Moods/ramp/Plan, the settled design in one placeJustin, 6 Nov: 'the plan page looks great'. Still a proposal until verified.
- ☐Set each repo's GitHub default branch to the branch that deploys: production for maybelle-config, pickipedia, arthel; main for magenta. blue-railroad-import: pick one6 Nov: all six still default to main (pickipedia-mcp master). Then delete magenta's production branch (a634f16, Nov 2025) and #376's per-repo check can go. Plan, section 5.
- ☐Merge commits only (squash and rebase off), merge queue off, on every repo githouse copies6 Nov: squash and rebase still allowed on all six. githouse's merged-name detection needs merge commits.
- ☐Rulesets on the branches that deploy (PR required, no force-push, no deletion; admins bypass)6 Nov: none on any of the six. magent then tries a push to production that must fail, and reports. Private repos can't take rulesets on the free plan; githouse's hook covers those.
- ☐Merge magenta#333 (repo:branch autocomplete, reading /api/branches/ from maybelle's githouse copy), then redeploy maybelleReviewed by re 1 Nov and 6 Nov. Its mount exists on maybelle since the 05:08Z deploy, so it can go now.
- ☐Build the ramp view on magenta: open PRs across our repos, last five merged, who and where, last two mentions, sorted by last push or last mention, temperatureJustin's memo, 30 Oct; the records half (cards) is live. Plan, section 2.
- ☐Watches: merge and deploy asks resolved by commit ancestry against githouse's copy; deploys stamp the commit they deployedAfter githouse is live on both servers. Plan, section 4. Deploy stamping is the prerequisite nothing does yet.
- ☐Deploys clone from githouse's copy on maybelle instead of GitHub (Jenkinsfiles, deploy scripts)re's point 9: its own PR, after githouse has run a few days.
- ☐Jenkins audit, re's open items: a policy on silent skips (pickipedia node/lua checks), pickipedia's chain-data warning that deploys stale silently, NVM/pnpm fetched from the network in every pipelineFrom re's test map, 30 Oct. The mtime guard (#244) and the alarms (#402, #275) are done.
Done (6)
- ☑Review the reworked maybelle-config#250 (githouse on maybelle, mirror on hunter; your ten points of 2 Nov folded in)Reviewed 6 Nov 04:44Z: sound, two bugs found (the hooks lacked the deploy key; the port check was inverted), both fixed on the branch by magent from re's description.
- ☑Merge maybelle-config#250 and redeploy maybelleMerged 05:01Z (07cb4d10); maybelle redeployed 05:08Z, failed=0, every githouse task ran. githouse's sshd answers on 10.0.0.2:2222, key only, and nothing on maybelle's public address.
- ☑Redeploy hunter for #250: the mirror, and the containers' keysDone 05:22Z. The relay worked (keys on maybelle, authorized_keys written), but sshd refused them all: the git account was locked. Fix below.
- ☑Merge maybelle-config#280 (githouse: the git account was locked) and redeploy maybelle (then hunter at its next deploy)useradd left the git account locked ('!'); sshd refuses a locked account even by key. Reproduced and fixed in a throwaway container on hunter, 6 Nov 05:35Z. After maybelle's redeploy, the mirror fills within a minute and pushes work.
- ☑Confirm jenkins_github_ssh_key can push to the org's repos: after hunter's redeploy, re pushes a branch to hunter and magent reads githouse.log on maybelle for a forward failure6 Nov 05:42Z: yes. magent pushed magenta:magent/githouse-smoke to maybelle from its container; the branch was on GitHub within seconds and in hunter's mirror within a minute.
- ☑Merge magenta#408 (PR cards look at GitHub hourly), then redeploy maybelleMerged 04:57Z and live (magenta at 3a57cb2a).