Caddy: route bare /me, /workspaces, /projects, etc. to backend

↗ view on GitHub · Claude · 2026-05-16 · 489196a2

The @backend path matcher only listed each prefix with /* (e.g.
/me/*), which in Caddy matches /me/onboarding-options but not the
bare /me. Bare-path requests were falling through to the Next.js
frontend, hitting the auth middleware, and 302-redirecting clients
back to /onboarding. This made the onboarding page hang at "Loading..."
after first sign-in: the form's /me fetch followed the redirect,
got HTML back, and the page never received an `onboarded` flag.

Express routers /me, /workspaces, /projects, /chat, /single-documents,
/tabular-review, and /workflows all expose list/create handlers on
the bare path, so each prefix is now listed both bare and with /*.

Operators who installed before this fix need to either re-run
install.sh (regenerates the Caddyfile) or edit
${DATA_ROOT}/caddy/Caddyfile by hand and `docker compose restart
caddy`.
Repository cpatpa/PIP
Author Claude <noreply@anthropic.com>
Authored
Parents b4a727b0
Stats 2 files changed , +18 , -8
Part of Caddy request dispatch (backend vs frontend on shared origin)

Capture this commit into my fork

Download a Markdown prompt that tells Claude how to port this exact commit into your working tree. Run it via claude -p < capture-commit-489196a2.md from inside the repo you want the change in.

⬇ Download capture-commit-489196a2.md