The .gitignore fix in 4b8277a was reverted by 0d243fc, which re-tracked
a root-level .next/ (258MB, 2521 files) that this repo never needed —
the Dockerfile only consumes build/ (the rsynced standalone output from
build.sh). With no .dockerignore, that dead weight plus .git (bloated
to 725MB from repeated .next churn) was shipped into every Docker build
context on Dokploy, causing build failures/timeouts that surfaced as a
502 after deploy.
.gitignore's ".next/" rule (no leading slash) matched at any depth, so
build/.next was silently excluded from every commit even though build.sh
populates it. The Docker image was built without the compiled server/static
output, so server.js had nothing to serve. Anchor the rule to the repo root
and commit the compiled output that Dokploy actually needs.
