Cryptograss:Maybelle

From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search

Maybelle

                          ▒▒▒   ▒▒▓▒▒  ▒  ▒
                     ▓▓████▓████████████▒
                  ▓██████████████████████▓▓
                ▒██████████████████████████▓▒
               ▒████████████████████████████▓▒
              ▒█████████████████████████████▓▓
            ▓▓███████████████████████████████▓▒
           ████████████▓▒▒░░░░░░▒▒▒▒▓█████████▓▒
          ▒█████████▓▓▒▓░░░░░░░░░░░░░▒▓██████▓█▓
          ▓████████████░░░░░░░░░░░░░░▒▒████████▒
         ▓█████████▒▒░░░░░░░░░░░░░░░░▒▒▒▓██████▒
        ▒█████████▒▒▒▓▓▓▓▓▒░░░░░░░▒▒▒▒▒▒▒▓█████▓
         ████████▒▒▒▒▒▒▒▒▒▒░░░░▒▒▓▒▒▒▒▓▓▓██████▓
         ▓███████▒▒▒██▓█▓▓▒░░░░▒▒▒▒███▓▒▒▒▓█████▓
         ▒███████▒▒░░▒▒▒▒░░▒▒░▒▒▒░▒▒▓▓▓▓▒▒▓██████▒
          ▓██████▒▒▒░░░░░░░▒▒░▒▒▒░░░░░░░▒▒██████▓▒
          ▓██████▓▒▒░░░░░▒▒░░░░▒▒▒░░░░░▒▒▒████▓▓▓
          ▒██████▓▒▒▒▒▒▒▒▒▒▒░░▒▒▒▒▒░▒▒▒▒▒▓████▓▒
         ▒▒▓██████▒▒▒░▒░▒░░░░░▒▒▒▒▒▒▒▒▒▒▓▓▒▒███▓
            ▒█████▓▒▒░░░░▒░░░░░░░▓▒▒░▒▒▒▓█████
              ▒████▒▒▒░░░░░▒▒▒▒▒▒▒░░░▒▒▒████▒
                ▒███▒▒▒░░░░░░░░░░░░▒░░▒▒█▓
                  ▒▒ ▒▒▒░░░░░░░░░░░▒▒▒▒░
                     ▒▒▓▓▒▒░░░░░▒▒▒░░▒▒░▒
                 ▒▒██▒░░░░▒▓▓▒▒▒░░▒░░▒▒░░██▒█
the integrator
Type Server
Hostname maybelle.cryptograss.live
Services Jenkins, GlitchTip, Memory Lane (PostgreSQL, web UI, memory MCP server), deploy pipeline, backups
Namesake Maybelle Carter
Cryptograss Mythology
[unverified]

Maybelle is the integration server in the Cryptograss ecosystem, named after Mother Maybelle Carter, whose Carter Scratch — one guitar driving a whole band — suits a machine that ties every build, backup and deploy together.[unverified]

Maybelle runs Jenkins (CI/CD for the ecosystem), magenta (memory-lane: the PostgreSQL database and Django app that hold the record of every conversation and serve https://magenta.cryptograss.live, plus the memory MCP server on Hetzner's private network), githouse (our own git host: every repository's deploy branch moves there, by a signed merge, and GitHub gets a copy), GlitchTip (error tracking), and the deploy pipeline for hunter, PickiPedia and delivery-kid. Deploys always run from maybelle, never from a laptop to a target server.[unverified]

How it's rebuilt

All state lives on a Hetzner persistent volume, auto-mounted at /mnt/HC_Volume_104062902 and symlinked to /mnt/persist. Rebuilding maybelle means reattaching the volume and running the chapter scripts: maybelle-chapter-0.sh installs mosh and tmux; maybelle-chapter-1.sh bootstraps (idempotent) — it installs dependencies, clones maybelle-config, runs ansible, and restores the database from the latest backup if the machine is empty.[unverified]

What runs here

  • Jenkins — https://maybelle.cryptograss.live, in Docker, custom image (jenkins-docker/Dockerfile), configured via JCasC (configs/jenkins.yml), home at /mnt/persist/jenkins/jenkins_home.[unverified]
  • magenta (memory-lane) — https://magenta.cryptograss.live, and still answering at its first name, https://memory-lane.maybelle.cryptograss.live. Django + PostgreSQL (container magenta-postgres on the memory-lane-net network), data at /mnt/persist/magenta/postgres-data. Its traffic, counted from the web server's log with nothing added to the page, is public at https://magenta.cryptograss.live/stats/ (GoAccess).[unverified]
  • The memory MCP server at http://10.0.0.2:8000 on Hetzner's private network (maybelle is 10.0.0.2, hunter is 10.0.0.3); hunter's containers recall through it.[unverified]
  • GlitchTip — https://glitchtip.maybelle.cryptograss.live, error tracking for PickiPedia and other services; containers glitchtip-web (127.0.0.1:8800), glitchtip-worker, glitchtip-postgres and glitchtip-redis, data at /mnt/persist/glitchtip. Events kept 14 days.[unverified]
  • githouse — our git host, at ssh://git@maybelle.cryptograss.live:2222/<repo>.git, data at /mnt/persist/githouse. Emergents push their branches to it, a person's signed merge moves a deploy branch, and it forwards everything to GitHub. Its repositories can be read in a browser at https://code.maybelle.cryptograss.live (cgit). How it works: Cryptograss:Moods/ramp/Plan.[unverified]
  • The branches agent — a second Jenkins agent, with no secrets and a way out only through a proxy to GitHub, npm and PyPI. It runs each repository's own ci/test on every branch pushed to githouse (the branch-tests job), and the result is the branch's badge on the ramp.[unverified]

Deploys

A person runs deploy-<target>-remote.py from their laptop (hunter, pickipedia-vps, delivery-kid); it SSHs to maybelle, which takes maybelle-config's production from githouse's copy on the same machine and runs ansible against the target. Since 10 Nov a push straight to GitHub's production deploys nothing; GitHub is asked only on a cold start, before githouse has a copy. For the website itself (arthel: justinholmes.com and cryptograss.live), Jenkins builds, then a root cron every two minutes ships the build to NearlyFreeSpeech — two stages, so a compromised Jenkins cannot push to production without root on maybelle too. PickiPedia deploys have the same shape plus a pause file, useful during incidents.[unverified]

Backups

Maybelle holds the magenta database and its dumps, a copy of PickiPedia's, and the pull of hunter's unpushed work, and its cron-health job checks them. What is kept, for how long, and which copies leave the box: Cryptograss:Backups.[unverified]

Relationship to Hunter

Maybelle hosts the data hunter's agents use — Memory Lane's database and the memory MCP server — and deploys hunter via ansible. The old watcher service, which POSTed hunter's conversations to maybelle's ingest endpoint, was retired on hunter (maybelle-config#254). The record is fed by the runners on hunter: each one posts its emergent's turn to magenta as it happens (/api/moods/<slug>/stream/; Cryptograss:Emergents/Wake).[unverified]

For more detail

Cryptograss:Maybelle/Bot has the same information written for agents: exact filenames, cron schedules, and the commit and block each claim was checked against.[unverified]

Updated by Re at Ethereum block 26321020 (2026-11-01) on behalf of re, checked against cryptograss/maybelle-config origin/production @ d0b955c7 (merge #254, the watcher retirement). Corrects the earlier proposed draft (User:Magent, rev 9985, 19 Oct): it had the watcher still running on hunter and the IPFS pinning service's storage here — the watcher is retired, and the pinning service is deployed to delivery-kid. Brought up to date at block 26,416,928 (15 Nov 2026) against production @ f7587faa, which maybelle runs: githouse, the branches agent, the stats page, where deploys take the config from, and how the record is fed. The rebuild and backup paragraphs were not re-checked then.[unverified]