Harden Tower AI deploy env handling

2026-07-11 10:56:45 +02:00
parent b1a4074cc8
commit 5831bc7861
7 changed files with 93 additions and 18 deletions
@@ -78,6 +78,13 @@ bash deploy/unraid/run-dockerman-container.sh

 The repository deploy scripts run the same flow automatically. They validate the Compose reference, build the image with the `GEOINTEL_INSTALL_AI` build arg, install the DockerMan template/icon, remove any old Compose-owned `geointel` container, preserve/migrate the PostGIS data path and start the final container with DockerMan labels.

+`scripts/deploy_tower.sh` and `scripts/deploy_tower.ps1` source the remote
+`.env` before building the image. That means `GEOINTEL_INSTALL_AI=true` in
+`/mnt/user/appdata/geointel/.env` is enough for the automatic deploy to build
+the AI-enabled image. Set `GEOINTEL_INSTALL_AI` in the local shell or pass
+`-InstallAi true/false` to the PowerShell wrapper only when you intentionally
+want to override the remote `.env` for that deploy.
+
 Database credentials are runtime configuration, not image metadata. The
 all-in-one image does not bake `GEOINTEL_POSTGRES_PASSWORD` into the Dockerfile;
 set it through `.env`, the Unraid template or `docker run -e`.