monster/Godstrument
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
93c5e20ccf
Godstrument/CLAUDE.md
type-two 8894cc11a5 🧭 fix deploy target in CLAUDE.md + track dev launch configs 
Verified live: godstrument.pro is served from the botchat VPS
(humanjing@100.71.119.27) via Cloudflare Tunnel, NOT dealgod — corrected the
canon note and recorded the rsync+restart deploy recipe. Also track the
godstrument-verify / -test launch configs.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-09 18:23:58 +10:00

1.1 KiB
Raw Blame History

Godstrument — Claude context

Music-instrument web app; hosted at godstrument.pro on the botchat VPS (humanjing@100.71.119.27, exposed via Cloudflare Tunnel — NOT dealgod, despite earlier notes). App dir /home/humanjing/godstrument (not a git checkout). Deploy = rsync git-tracked files only (--files-from=<(git ls-files), never --delete, never push godstrument_users.db/auth_secret/patches/) then sudo -n systemctl restart godstrument. Origin is Gitea ssh://git@100.71.119.27:222/monster/Godstrument.git. See godstrument-pro-deploy.

  • Canon gotcha: the real spec prose lives in viz/index.html (grimoire text around line ~950); GODSTRUMENT_MANUAL_SOURCE.md claims to be exhaustive but has drifted before (Earth Echo / Schumann layer was missing). When they disagree, viz/index.html is truth — update the manual to match, not the other way.
  • Secrets (Cloudflare token etc.): read from .env/local files, never from chat. A CF token was pasted in chat once and rolled — don't repeat that.
  • First page load after a deploy is slow (cold start) — wait before declaring it broken.