Revert the CI full-fetch workaround and drop the dead Caddyfile

Shallow clones were never a Gitea packing bug. An intruder had set uploadpack.packObjectsHook in Gitea's HOME gitconfig, pointing at a non-executable dropper, so every upload-pack died mid-pack. That hook is gone and --depth=1 clones are verified working, so fetch-depth: 0 buys nothing but slower CI. See INCIDENT-2026-08-11.md. infra/Caddyfile was dead: ansible templates Caddyfile.j2 to /etc/caddy/Caddyfile, and nothing ever deployed the static copy. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-16 12:59:52 -04:00
parent 518ac46929
commit a0a414ad21
2 changed files with 0 additions and 20 deletions
@@ -1,14 +0,0 @@
-# Managed by CI — deployed to /etc/caddy/Caddyfile on the server.
-# Caddy handles TLS automatically via Let's Encrypt.
-
-api.{$DRB_DOMAIN} {
-  reverse_proxy localhost:8888 {
-    header_up X-Forwarded-For {remote_host}
-  }
-}
-
-app.{$DRB_DOMAIN} {
-  reverse_proxy localhost:3000 {
-    header_up X-Forwarded-For {remote_host}
-  }
-}