If Saxon dies — GitHub
GitHub holds source code for SaxDocs, SaxWeather, and dozens of other projects under github.com/saxobroko. SaxDocs auto-deploys to docs.saxobroko.com on every push to main — that pipeline can keep running if the account, billing, and secrets are maintained.
Ryan inherits the physical tech per the will. This page covers GitHub and SaxDocs continuity, not money or domain login (see First 24 hours and Cloudflare account access).
Why GitHub matters
| Item | Why survivors care |
|---|---|
| SaxDocs repo | These guides live here — edits deploy to the live site |
| GitHub Actions | Builds MkDocs and pushes to Cloudflare Pages |
| Secrets | Cloudflare token for deploy — not in the repo |
| Other repos | SaxWeather, website, SaxoStatus — public face of saxobroko.com |
| Billing | Account must stay in good standing (free tier covers much of this) |
Find GitHub login
- Vaultwarden — search GitHub.
- Username is typically saxobroko.
- 2FA uses YubiKey — YubiKey. Without YubiKey, use GitHub account recovery with Saxon's email access (handled in handover docs).
Key repositories
| Repo | URL | Role |
|---|---|---|
| SaxDocs | github.com/saxobroko/SaxDocs | This documentation site |
| SaxWeather | github.com/saxobroko/SaxWeather | Weather app — most active |
| SaxoStatus | github.com/saxobroko/SaxoStatus | status.saxobroko.com |
| Website | github.com/saxobroko/saxobrokowebsite | Main site source |
Full catalogue: Projects.
How SaxDocs keeps deploying
Edit markdown in SaxDocs → push to main
→ GitHub Actions runs mkdocs build
→ wrangler deploys to Cloudflare Pages (project: saxdocs)
→ docs.saxobroko.com updates
No home NAS required for SaxDocs hosting — only for homelab content pages that describe NAS services.
Check deploy health:
- github.com/saxobroko/SaxDocs/actions
- Cloudflare → Workers & Pages → saxdocs → Deployments
Details: This docs site, Cloudflare Pages.
Secrets that must survive
Stored in GitHub → SaxDocs → Settings → Secrets and variables → Actions:
| Secret | Purpose |
|---|---|
CLOUDFLARE_API_TOKEN |
Upload built site to Pages |
CLOUDFLARE_ACCOUNT_ID |
Target Cloudflare account |
CLOUDFLARE_ZONE_ID |
Optional DNS cleanup |
If deploys fail with auth errors:
- Log into Cloudflare — Cloudflare account access.
- Create a new API token with Cloudflare Pages Edit (same template as original setup).
- Update GitHub secrets — you need repo admin access.
Token creation steps: Cloudflare reference — do not paste tokens into SaxDocs.
Transferring or sharing the account
Options (legal/estate planning is outside this doc):
| Approach | Notes |
|---|---|
| Ryan uses existing saxobroko account | Simplest for deploy continuity — credentials + YubiKey from estate |
| Add Ryan as collaborator on SaxDocs | Can push docs; secrets still need admin to rotate |
| Transfer repos to Ryan's GitHub user | Updates remotes, secrets, Pages project links — plan carefully |
Do not delete the saxobroko GitHub account
That removes repos, breaks Actions history, and may unlink Cloudflare Pages. Archive or transfer instead.
Editing SaxDocs after Saxon is gone
- Clone or edit on GitHub web UI: github.com/saxobroko/SaxDocs.
- Markdown files live under
docs/. - Commit to
main— production branch; every push deploys. - Preview locally if needed:
pip install -r requirements.txt && mkdocs serve— This docs site.
Will and handover content can be updated to reflect reality — follow Read the will rules about conflicting edits.
Billing
- Public repos and Actions minutes are generous on free plans.
- If GitHub invoices a paid feature, payment method on file must stay valid — check Settings → Billing after account access.
- Cloudflare Pages for SaxDocs has its own Cloudflare account — not GitHub billing.