dev-ops

Projects using dev-ops

Project Actions builder Cloud environment Notes
edsaperia/dev-ops wiring 2026-09-26 (the test bed) — no build; the builder only edits markdown here
edsaperia/draft (docs.vote) wiring 2026-09-26 network Custom + cdn.playwright.dev; setup script npx -y playwright@1.62.1 install chromium a push to main deploys docs.vote; the Playwright version in the setup script must follow package.json; the project’s CLAUDE.md is long and authoritative
edsaperia/mergetournament (mergetournament.org) wired and tested 2026-09-26 (Node 24, npm ci) — a push to main deploys mergetournament.org (.github/workflows/deploy.yml, SSH to the droplet running deploy/update.sh), except pushes touching only markdown or docs/; tests use embedded PGlite, so no database service is needed; builders have no browser, so UI changes need a click-through before deploy
nwspk/admit (private: the spec, BUILD-PLAN.md and coordination) + code in nwspk/web (the newspeak.house Rails site, at newspeak.house/admissions; Ed’s ruling Q32, 2026-10-02) not wired same environment; CLAUDE_CODE_PLUGIN_DIRS carries admit’s page-guard path in nwspk/web a push to master deploys newspeak.house and staging deploys the staging droplet, and CI runs no tests (deploys only), so every merge there is a Merge question with a staging check first; the site’s server and database are run by @sirodoht (nwspk/web#52), so his PRs and infrastructure are his; nwspk/admit itself deploys nothing (the coordinator merges Ed’s chosen changes there); its GitHub tool reaches only nwspk, so it reads dev-ops by public clone; coordinator started 2026-10-02 (session_01VPkrCuL6Ych9eNkhvd7pyw)
sugaroverflow/timetable (Topic, renamed from Timetable; topic.forum) the Claude GitHub app is not installed (repo on sugaroverflow’s personal account; issue #363 asks), so no GitHub events reach its sessions; pushes and PRs work through Ed’s GitHub link same environment; CLAUDE_CODE_PLUGIN_DIRS carries /home/user/timetable/...; Node 20+ monorepo, Playwright merging to main deploys dev (dev.timetable.love) after CI verify, and CI runs only when code paths change; production deploys only by Ed running deploy-production.yml; squash merges; other contributors’ PRs are theirs; additive-only migrations in term; coordinator started 2026-10-02 (session_01SFYjPigdVEgvyXT9D3kouX)
edsaperia/ae (private; Ed and gutterv’s shared space for organising shared projects) not wired; the Claude app reaches it (PR events arrive) same environment; CLAUDE_CODE_PLUGIN_DIRS carries /home/user/ae/... nothing deploys; two equal owners: CLAUDE.md is shared, and each owner’s sessions read only their own people/<owner>.md (Ed’s holds his page and the dev-ops rules); gutterv doesn’t see Ed’s page, so anything for them goes in the PR; coordinator started 2026-10-02 (session_01YEdDwCggA4WEbNkux9K8x9)
edsaperia/witch (Witch, a new videogame; public) not wired same environment; CLAUDE_CODE_PLUGIN_DIRS carries /home/user/witch/... once Ed adds it nothing deploys from main yet; Ed created the repository himself (2026-10-03), since a cloud session cannot; Witch puts nothing on Ed’s questions page for now (questions, tasks, updates, builders’ finished cards): Ed works with its coordinator directly in that session (Ed, 2026-10-05); builders still wake the coordinator directly; this lasts until Ed says otherwise; coordinator started 2026-10-03 (session_01SzjrULBxoRwTPW2F6P3sSi)