No description
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
All checks were successful
Deploy / deploy (push) Successful in 6s
Forgejo SSH has to reach the origin directly. Cloudflare's edge exposes no public SSH listener - a tunnel can carry TCP, but only when `cloudflared access` runs on the connecting machine to wrap the stream. Outside collaborators won't install that, so git.bobparsons.dev moved back to a grey A record and now carries the WAN IP. Side benefit: pushes no longer traverse the proxy, so the 100MB request body cap doesn't apply to git over HTTPS either. Cost: the Forgejo web UI loses Cloudflare's WAF. Forgejo's own auth is the remaining gate, as it was before the migration. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
| .forgejo/workflows | ||
| docs | ||
| .env.example | ||
| .gitignore | ||
| CLAUDE.md | ||
| config.yml | ||
| config.yml.backup | ||
| cspell.json | ||
| docker-compose.yaml | ||
| logrotate.conf | ||
| README.md | ||
| traefik-hybrid-plan.md | ||
| traefik.yml | ||
| traefik.yml.backup | ||
traefik
Traefik is deployed through the Forgejo workflow at .forgejo/workflows/deploy.yml.
Deployment configuration and required Infisical secrets are documented in docs/deployment.md.