06 · Current Status
Live inventory (2026-09-19)
Section titled “Live inventory (2026-09-19)”| 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 one open security item
Section titled “⚠️ The one open security item”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)”- Cloudflare dashboard → Zero Trust (first time: pick a team name, e.g.
sambasene— your login domain becomessambasene.cloudflareaccess.com) - Access → Applications → Add an application → Self-hosted
- Domain:
sambasene-private-docs.pages.dev - Policy → Allow — include your email(s), identity provider Email OTP (simplest, no client)
- 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.
Manual items still open
Section titled “Manual items still open”- GitHub login + repos created (branch fixation to
maindone) - 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) |
Gotcha register (so far)
Section titled “Gotcha register (so far)”- npm 11
allow-scriptsguard blocks native install scripts → approve + persist inpackage.json create-astroinits repos onmaster; workflows onmain→ rename branch, fix GitHub default, delete remotemasterghin this agent shell needsGH_CONFIG_DIR=$HOME/.config/gh- wrangler 4.x does NOT auto-create Pages projects → create explicitly
wrangler-actioninputs are not shells → no|| trueincommand:; use arun:step*.pages.devnames are globally unique → unique project names, or a custom domainpkill -fcan self-match its own command line → kill by PID- Agent shell runs in a Flatpak (Freedesktop SDK) runtime → host installs happen in the user’s terminal
Where the docs go from here
Section titled “Where the docs go from here”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.