fix: enforce isolated beta deployment path

2026-09-17 22:41:34 +12:00
parent 2525a9eb25
commit 91a950a3b0
2 changed files with 2 additions and 2 deletions
@@ -178,9 +178,10 @@ The existing `PROD_*` names are retained for compatibility, but this workflow us
 - `PROD_SSH_PRIVATE_KEY`: private key for the deployment account.
 - `PROD_SSH_HOST`: target host, for example `AMS-DEV01`.
 - `PROD_SSH_USER`: target user, for example `zak`.
- `PROD_DEPLOY_PATH`: beta app path, for example `/home/zak/magent-beta`.
 - `PROD_SSH_KNOWN_HOSTS`: required pinned `known_hosts` entry. Deployments reject unknown or changed hosts.

+Beta always deploys to the isolated `/home/<deployment-user>/magent-beta` directory; the production path secret is intentionally ignored.
+
 ## Security and data handling

 Generate independent signing and settings-encryption secrets before first startup: