e22aeb9b5a
- backend/Dockerfile: split builder/runner, runtime libs only, non-root app user, curl for healthcheck, --frozen via new uv.lock - frontend/Dockerfile: npm ci instead of npm install (deterministic), USER node - docker-compose.prod.yml: working backend healthcheck (curl now in image), redis healthcheck, drop dead NEXT_PUBLIC_API_BASE_URL env (Next.js bakes NEXT_PUBLIC_* at build time, runtime override is no-op) - docker-compose.yml: same redis healthcheck, BACKEND_URL for next.config rewrites, drop uv from CMD (not in new image) - Caddyfile: handle (not handle_path) so /api prefix is preserved into FastAPI router - next.config.ts: rewrite /api/* and /health to BACKEND_URL in dev (no Caddy locally) - frontend/src/lib/api.ts: empty default = same-origin relative URLs - Makefile: drop uv run from migrate target - Add backend/uv.lock and frontend/package-lock.json for reproducible builds Verified: docker build succeeds for both, backend container starts, /health responds, curl healthcheck works inside image, container runs as non-root. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
19 lines
664 B
TypeScript
19 lines
664 B
TypeScript
import type { NextConfig } from "next";
|
|
|
|
const nextConfig: NextConfig = {
|
|
reactStrictMode: true,
|
|
output: "standalone",
|
|
// In dev (no Caddy) Next.js itself proxies /api/* and /health to the backend
|
|
// so the browser can use same-origin relative URLs.
|
|
// In prod Caddy intercepts these paths before they reach Next.js,
|
|
// so these rewrites are effectively a no-op there.
|
|
async rewrites() {
|
|
const backend = process.env.BACKEND_URL ?? "http://localhost:8000";
|
|
return [
|
|
{ source: "/api/:path*", destination: `${backend}/api/:path*` },
|
|
{ source: "/health", destination: `${backend}/health` },
|
|
];
|
|
},
|
|
};
|
|
|
|
export default nextConfig;
|