enable react compiler

2026-06-27 00:05:42 -04:00
parent b9a9b813d2
commit 5e6e51337a
8 changed files with 283 additions and 35 deletions
@@ -130,8 +130,23 @@ NEXT_PUBLIC_UMAMI_SCRIPT_URL=https://analytics.umami.is/script.js
 # =============================================================================
 # Receipt storage — S3-compatible (optional)
 # =============================================================================
-# When unset, receipt files are stored locally in .data/receipts/ (dev-friendly).
-# Works with AWS S3, MinIO, Cloudflare R2, etc.
+# When S3_BUCKET + S3_ACCESS_KEY + S3_SECRET_KEY are unset, receipts land in
+# .data/receipts/ (dev-friendly). Works with AWS S3, MinIO, Cloudflare R2, etc.
+#
+# S3_ENDPOINT — who can reach MinIO?
+#   • Host dev (bun dev + docker-compose.dev.yml MinIO on the host): localhost:9000
+#   • App in Docker (docker-compose.yml): http://minio:9000 (Compose service name)
+#   • Coolify — see docs/COOLIFY.md for full steps. Summary:
+#     - Best: one Compose resource with docker-compose.yml (app+db+minio); do not override S3_ENDPOINT.
+#     - App + separate MinIO stack: ENOTFOUND minio means the app is not on MinIO's Docker network.
+#       Fix: Beevoice Application → enable "Connect to Predefined Network" (same destination as MinIO),
+#       set S3_ENDPOINT=http://<internal-host-from-minio-ui>:9000 (often NOT bare "minio").
+#     - NEVER use localhost in production — inside the app container that is the app, not MinIO.
+#   Troubleshooting getaddrinfo ENOTFOUND minio:
+#     1) Confirm Beevoice and MinIO are same Coolify project/destination
+#     2) Enable Connect to Predefined Network on Beevoice; redeploy
+#     3) Copy hostname from MinIO resource internal URL → S3_ENDPOINT (http://HOST:9000)
+#     4) Or deploy docker-compose.yml as a single stack instead
 #
 # Local dev with docker-compose.dev.yml MinIO (host `bun dev`):
 S3_ENDPOINT=http://localhost:9000