From a0a414ad2109fdb4950f0aba6f16ed4b6d9ad567 Mon Sep 17 00:00:00 2001 From: Logan Cusano Date: Sun, 16 Aug 2026 12:59:52 -0400 Subject: [PATCH] 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 --- .gitea/workflows/deploy.yml | 6 ------ infra/Caddyfile | 14 -------------- 2 files changed, 20 deletions(-) delete mode 100644 infra/Caddyfile diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index fa31532..e2a4174 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -14,13 +14,7 @@ jobs: runs-on: ubuntu-latest steps: - # fetch-depth: 0 on purpose. The default depth=1 shallow fetch made Gitea - # die generating the pack ("fatal: protocol error: bad pack header", - # retried three times and failed the run). A full fetch takes the slow - # path on the server and works. Don't "optimise" this back to depth=1. - uses: actions/checkout@v4 - with: - fetch-depth: 0 - name: Set up Docker Buildx uses: docker/setup-buildx-action@v3 diff --git a/infra/Caddyfile b/infra/Caddyfile deleted file mode 100644 index 6220bb8..0000000 --- a/infra/Caddyfile +++ /dev/null @@ -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} - } -}