docs(deploy): the live instance now runs APP_ENV=production

Set APP_ENV=production in the host's deploy/.env (it had been left at the
.env.example default) and recreated backend + worker; /health now reports
"env":"production". Update the README note accordingly.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01BeRh7Vwq8j9s6jshaMUNCd
Signed-off-by: Justin Paul <[email protected]>
This commit is contained in:
2026-09-20 22:45:14 -04:00
co-authored by Claude Opus 5
parent f9344ac317
commit a56be69a8b
+3 -4
View File
@@ -42,7 +42,6 @@ Justin's own deployment — the one holding the Paul/Reier family tree:
Health check (no auth): `curl https://provenance.paul.farm/health`. Health check (no auth): `curl https://provenance.paul.farm/health`.
Known drift: that endpoint currently reports `"env":"development"` — the host's It reports `"env":"production"` — the host's `.env` sets `APP_ENV=production`
`.env` never set `APP_ENV=production`. It is informational only (`app_env` is (corrected 2026-09-20; it had been left at the `.env.example` default). `app_env`
reported by `/health` and `/api/v1/admin`; it gates no behavior), but it should is informational: `/health` and `/api/v1/admin` report it, nothing branches on it.
be corrected on the host.