Implement Caddy with Gitea so git.inviscid.net is server over hostname-based HTTPS with automatic certificate renewal.
Acceptance criteria:
git.inviscid.net resolves to the EC2 Elastic IP from an independent resolver.
Caddy proxies to gitea:3000 over the private Compose network.
Gitea DOMAIN and ROOT_URL are set to the HTTPS hostname.
A valid Let's Encrypt certificate is served; issuer and expiry are recorded.
http://git.inviscid.net redirects to HTTPS.
Certificate state persists in a named volume across Caddy container replacement.
Implement Caddy with Gitea so git.inviscid.net is server over hostname-based HTTPS with automatic certificate renewal.
Acceptance criteria:
- [x] git.inviscid.net resolves to the EC2 Elastic IP from an independent resolver.
- [x] Caddy proxies to `gitea:3000` over the private Compose network.
- [x] Gitea `DOMAIN` and `ROOT_URL` are set to the HTTPS hostname.
- [x] A valid Let's Encrypt certificate is served; issuer and expiry are recorded.
- [x] `http://git.inviscid.net` redirects to HTTPS.
- [x] Certificate state persists in a named volume across Caddy container replacement.
payton
self-assigned this 2026-10-15 23:12:12 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Implement Caddy with Gitea so git.inviscid.net is server over hostname-based HTTPS with automatic certificate renewal.
Acceptance criteria:
gitea:3000over the private Compose network.DOMAINandROOT_URLare set to the HTTPS hostname.http://git.inviscid.netredirects to HTTPS.Enable HTTPS for git.inviscid.netto Enable HTTPS for git.inviscid.dev