dash.foogy
concept updated 2026-07-04 live

cloudflare-deploy

Summary: foogy’s sites deploy via Cloudflare Pages + Git integration (push main → build → deploy); the D1-backed dashboard detour FAILED because the automation sandbox can’t reach the Cloudflare API, so knowledge/state stays on plain files.

How the deploy works (the working path)

  • foogy-dev (foogy.xyz) is an Astro static site on Cloudflare Pages.
  • As of 2026-06-29 the Pages project is connected to GitHub (mfugaj/foogy.dev, production branch main, build npm run build, output dist).
  • Pushing to main auto-deploys. No manual wrangler pages deploy — the old project used direct upload, which is why pushes didn’t deploy before the Git connection.
  • Source: memory/foogy-dev-deploy.md; foogy.dev/docs/home-restructure-plan.md (§deploy).

The D1 dashboard detour (FAILED — lesson)

The control-center pipeline briefly moved its task dashboard onto a Cloudflare D1 database (dash-foogy-db) behind Cloudflare Access. Every scheduled dispatcher run since could NOT reach it:

  • The sandbox where crons run can reach github.com over git but NOT api.cloudflare.com / pages.dev / api.github.com (proxy allowlist). So wrangler and any CF/GitHub API call fail from there.
  • Only the main interactive session had the Cloudflare connector; the scheduled/sandbox runs had a GitHub token only, and the D1 site sat behind Cloudflare Access.
  • Result: ~20+ consecutive dispatcher runs logged “live D1 (dash-foogy-db) unreachable from sandbox … Nothing to dispatch.” The automation was effectively blind to its own state store.
  • Source: control-center/runs.log (2026-07-02 → 2026-07-04 entries).

Lesson

Keep the dashboard / knowledge / task state on plain files the automation can read directly (git-tracked markdown), not a DB the scheduled sandbox can’t reach. Anything gated behind Cloudflare Access + an API the cron can’t call is invisible to the pipeline. This “second brain” vault is the plain-file replacement.

Sources

  • memory/foogy-dev-deploy.md
  • ~/Documents/localhost/control-center/runs.log
  • ~/Documents/localhost/foogy.dev/docs/home-restructure-plan.md
  • Related: foogy-dev