Aravind
befe4307c3
The deployed console called its own origin instead of the platform. The BFF
route would throw "LOYALY_API_BASE is required in production — refusing to
guess the Loyaly platform host", and from the browser that reads as a broken
login form rather than as a missing variable.
The guard was right; nothing ever set the variable. `.gitignore` had a blanket
`.env*` and `.dockerignore` excluded `.env` and `.env.*`, so the image carried
no environment at all and the only copy of the production host was a comment
in `.env.example`. Injecting it by hand at the orchestrator was the single
point of failure, and it failed.
The platform host is not a secret, so it is now committed in `.env` and copied
into the runner stage. `next build` does not fold `.env` into
`.next/standalone`, which is why the COPY is explicit; server.js chdirs to
/app and Next runs loadEnvConfig there, so the file sits beside it at the
WORKDIR root. `npm run bundle` stages it the same way for a non-Docker deploy.
This pins nothing. @next/env never overwrites a variable already present in
process.env, so anything set in Dokploy still wins — verified against
@next/env directly: a bare image resolves https://mcp.loyaly.ai, an injected
LOYALY_API_BASE overrides it, and a leaked .env.local beats both.
That last case is why `.dockerignore` still excludes `.env.*`. A developer's
.env.local points at http://127.0.0.1:8088 and loads AHEAD of .env, so one
leaking into the build context would make the deployed console call localhost
with no error to read. Confirmed the context now carries `.env` and nothing
else.
AUTH_SECRET stays out of every committed file and out of the image. It signs
the session cookie and encrypts the token bundle, so a committed value is a
session-forging key in git — the thing 8b3fbab removed from the Dockerfile.
It remains a Dokploy secret, and production still refuses to sign without it.
`.env.example` is now the template for `.env.local` rather than a second copy
of the production values, so the two files cannot drift.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
57 lines
3.2 KiB
Bash
57 lines
3.2 KiB
Bash
# ---------------------------------------------------------------------------
|
|
# Production runtime configuration. COMMITTED ON PURPOSE — carries no secret.
|
|
# ---------------------------------------------------------------------------
|
|
#
|
|
# This file is the production environment. It is read by `next build` and, more
|
|
# importantly, by the standalone `server.js` at boot (Next calls loadEnvConfig
|
|
# on the server's working directory), so the deployed container knows the
|
|
# platform host without anyone remembering to type it into a dashboard.
|
|
#
|
|
# ── Precedence, exactly as @next/env resolves it ────────────────────────────
|
|
#
|
|
# 1. real process.env (Dokploy / docker -e / systemd) ← always wins
|
|
# 2. .env.production.local
|
|
# 3. .env.local ← LOCAL DEV ONLY. Never enters the image.
|
|
# 4. .env.production
|
|
# 5. .env ← this file, the floor everything falls back to
|
|
#
|
|
# A value already present in process.env is never overwritten by a file, so
|
|
# setting LOYALY_API_BASE in Dokploy still overrides this — nothing here locks
|
|
# the deployment in. It only removes "unset" as a possible state.
|
|
#
|
|
# ── Working on this locally? ────────────────────────────────────────────────
|
|
# Put your overrides in `.env.local` (gitignored, loaded ahead of this file).
|
|
# Without one, `npm run dev` will talk to the PRODUCTION platform, because that
|
|
# is what this file says. `.env.example` has the local values to copy.
|
|
|
|
# The one shared Loyaly platform API (Behavision). Server-side only and
|
|
# deliberately NOT NEXT_PUBLIC: publishing the host would let a browser bypass
|
|
# the BFF, which is what keeps the access token out of JavaScript.
|
|
#
|
|
# NOT platform.loyaly.ai — that host serves THIS console, not the API. Pointing
|
|
# the variable there makes the BFF call its own origin, which fails in a way
|
|
# that looks like a broken login form rather than a misconfiguration.
|
|
# apiClient.ts rejects that hostname by name for exactly this reason.
|
|
LOYALY_API_BASE=https://mcp.loyaly.ai
|
|
|
|
# Browser → this app's own BFF routes, which are same-origin. Empty is correct
|
|
# and is what makes the console work on any hostname it is served from:
|
|
# requests go to /api/... on whatever origin loaded the page (localhost:3100 in
|
|
# dev, platform.loyaly.ai in production) and the server hop above reaches the
|
|
# platform. Setting this to the platform host would send the browser straight
|
|
# at the API with no session cookie and no token — do not.
|
|
#
|
|
# It is NEXT_PUBLIC, so it is inlined at BUILD time, not read at runtime.
|
|
# Changing it in Dokploy's environment panel would do nothing without a rebuild.
|
|
NEXT_PUBLIC_API_BASE=
|
|
|
|
# AUTH_SECRET is deliberately NOT in this file.
|
|
#
|
|
# It signs the session cookie and encrypts the platform token bundle, so a
|
|
# value committed here is a session-forging key in git — anyone who can read
|
|
# the repo could mint a cookie for any user. It was already removed from the
|
|
# Dockerfile once for that reason; do not reintroduce it here.
|
|
#
|
|
# Set it as a Dokploy environment variable / secret. Production refuses to sign
|
|
# sessions without it. Generate with: openssl rand -base64 48
|