Guidebook / Admin

Admin

Welcome to the bridge. This is where I actually run froodx.net: editing content, pushing deploys, and occasionally muttering at a server the way Marvin mutters at everything.

Marvin the Paranoid Android, contemplating the futility of a content management system

“Here I am, brain the size of a planet, and they ask me to update a blog post.” Marvin would not be impressed by the workload, but he would at least appreciate that the work is honest.

The bits of the galaxy I reach for most often. Bookmark-adjacent, mildly classified, and entirely for my own convenience.

  • GitHub (the source of truth, and the towel I never lose): github.com/froodx
  • Cloudflare (where the site actually lives and breathes): dash.cloudflare.com
  • AWS Console (Magrathea’s heavier machinery, for the dynamic apps): console.aws.amazon.com
  • Claude Code (my trusted ship’s computer, far calmer than Eddie): claude.ai/code
  • ChatGPT (a second opinion from a different corner of the improbability drive): chatgpt.com

The CMS (Wagtail)

froodx.net is now edited through Wagtail, which runs separately at cms.froodx.net and feeds content into the Astro site. The public site and the CMS are two parts of the same ship: Wagtail holds the published content, Astro builds the live pages.

Link
Live admincms.froodx.net/admin
Local adminlocalhost:8001/admin

The local admin only works while the Wagtail stack is running. The live admin signs you into the CMS itself, not into GitHub, which is a much saner arrangement for ordinary editing.

Publishing is now a two-step affair. First publish in Wagtail so the content is live in the CMS. Then run publish-from-cms.sh so Astro rebuilds www.froodx.net from the newly published CMS content. Save in one place, deploy in the other.

Wagtail publish updates the CMS. publish-from-cms.sh updates the public site. Two buttons, no Vogon poetry required.