Skip to content

06 · Current Status

Item Value
Public repo sambaseness/public-docs (PUBLIC)
Private repo sambaseness/private-docs (PRIVATE)
Public site https://sambasene-public-docs.pages.dev (Astrogon)
Private site https://sambasene-private-docs.pages.dev (Starlight)
CI ✅ green (both) — npm ci && npm run build
CD ✅ green (both) — wrangler-action → Cloudflare Pages
Local dev npm run dev → :4321 (public) / :4322 (private)

The private site currently has NO auth gate. Until the Access application is attached, it is public on the internet (content is still template stubs, but apply the gate before real content goes in).

Steps — attach Cloudflare Access (5 minutes)

Section titled “Steps — attach Cloudflare Access (5 minutes)”
  1. Cloudflare dashboard → Zero Trust (first time: pick a team name, e.g. sambasene — your login domain becomes sambasene.cloudflareaccess.com)
  2. Access → Applications → Add an application → Self-hosted
  3. Domain: sambasene-private-docs.pages.dev
  4. Policy → Allow — include your email(s), identity provider Email OTP (simplest, no client)
  5. Save → verify: sign out, reopen the URL → your login page, your email passes

Optional later: install WARP (sudo dnf install cloudflare-warp on Fedora, key rotation required if the repo predates 2025-09-12) and add a device-posture rule.

  • GitHub login + repos created (branch fixation to main done)
  • Secrets added to both repos
  • First deploys green on unique names
  • Cloudflare Access application on the private site ← do this next
  • Optional: delete ghost projects public-docs / private-docs (dashboard → Workers & Pages → Overview) — redundant leftovers from the first deploys
  • Custom domain (kills the pages.dev namespace issue permanently, adds branding)
  • Real content (replace Astrogon/Starlight template content)
  • Scrum board + issue templates + labels on GitHub

The Scrum/Agile plan (native GitHub, free)

Section titled “The Scrum/Agile plan (native GitHub, free)”
Ceremony GitHub mechanism
Backlog Issues with labels (content, docs, bug, priority, p1…)
Sprints (1–2 wks) Milestones, or Project Iteration field
Board Project: Backlog → Ready → In Progress → Review → Done; automations move cards when linked PRs open/close
Definition of done Merged to main + CI green (branch protection: PR + status check required)
  1. npm 11 allow-scripts guard blocks native install scripts → approve + persist in package.json
  2. create-astro inits repos on master; workflows on main → rename branch, fix GitHub default, delete remote master
  3. gh in this agent shell needs GH_CONFIG_DIR=$HOME/.config/gh
  4. wrangler 4.x does NOT auto-create Pages projects → create explicitly
  5. wrangler-action inputs are not shells → no || true in command:; use a run: step
  6. *.pages.dev names are globally unique → unique project names, or a custom domain
  7. pkill -f can self-match its own command line → kill by PID
  8. Agent shell runs in a Flatpak (Freedesktop SDK) runtime → host installs happen in the user’s terminal

This build-log is the first real content. Natural next pages: access-setup.md (once the gate is on), scrum-workflow.md (once the board exists), and the actual product documentation the site is for.