Nicolas Pastorello e912ef2c1b feat: add optional Docker / Docker Compose support ... Give forkers who self-host on their own infra a first-class container path instead of hand-rolling a Dockerfile and guessing the Next.js standalone wiring. - Multi-stage Dockerfile (deps -> build -> runtime) using Next.js output: "standalone"; runs as a non-root user. - Single-service docker-compose.yml — Supabase stays external, so no database container is included. - .dockerignore and docs/docker.md documenting the setup, including the build-time (NEXT_PUBLIC_*, inlined into the client bundle) vs runtime (server secrets via env_file) split. - Set output: "standalone" in next.config.ts. This is a no-op for next start and the Hostinger path; only the Docker build consumes it. Purely additive: no dependency or stack changes, existing deploy paths are unaffected. Database migrations remain out of scope for the container (applied via the Supabase CLI, matching the external-Supabase model).		2026-07-29 13:54:30 -03:00
..
docker.md	feat: add optional Docker / Docker Compose support	2026-07-29 13:54:30 -03:00
mcp.md	Add MCP server for the public API	2026-07-08 17:30:24 +03:00
public-api.md	feat(api): outbound event webhooks — /api/v1/webhooks (#245)	2026-07-01 14:53:18 +03:00