From a56be69a8b1aa01f5108b833ffe9ae18cbf83c94 Mon Sep 17 00:00:00 2001 From: Justin Paul Date: Sun, 20 Sep 2026 22:45:14 -0400 Subject: [PATCH] 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) Claude-Session: https://claude.ai/code/session_01BeRh7Vwq8j9s6jshaMUNCd Signed-off-by: Justin Paul --- deploy/README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/deploy/README.md b/deploy/README.md index 3431c89..1fb9c24 100644 --- a/deploy/README.md +++ b/deploy/README.md @@ -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`. -Known drift: that endpoint currently reports `"env":"development"` — the host's -`.env` never set `APP_ENV=production`. It is informational only (`app_env` is -reported by `/health` and `/api/v1/admin`; it gates no behavior), but it should -be corrected on the host. +It reports `"env":"production"` — the host's `.env` sets `APP_ENV=production` +(corrected 2026-09-20; it had been left at the `.env.example` default). `app_env` +is informational: `/health` and `/api/v1/admin` report it, nothing branches on it.