From 4f23b0cd9d82f23af9517ef8831e38689c316644 Mon Sep 17 00:00:00 2001 From: Codex Date: Wed, 17 Jun 2026 06:10:56 +0200 Subject: [PATCH] Record Docker secret hygiene verification --- docs/CODEX_EXECUTION_LOG.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/CODEX_EXECUTION_LOG.md b/docs/CODEX_EXECUTION_LOG.md index 6c41e6ea..53a369b3 100644 --- a/docs/CODEX_EXECUTION_LOG.md +++ b/docs/CODEX_EXECUTION_LOG.md @@ -1613,10 +1613,14 @@ Tested: - `cd frontend && npm run build` - `bash scripts/run_readiness_check.sh` - `cd backend && python -m alembic heads && python -m alembic upgrade head --sql` +- `powershell -NoProfile -ExecutionPolicy Bypass -File scripts/deploy_tower.ps1` +- `bash scripts/verify_browser_runtime.sh http://192.168.10.150:1202` +- `bash scripts/verify_gis_runtime.sh http://192.168.10.150:1202` +- `bash scripts/verify_demo_export_workflow.sh http://192.168.10.150:1202` Open: - Local Windows shell has no `docker` command in PATH, so Docker build/config verification must run on Tower during deploy. -- Rebuild the Tower image and confirm the Docker BuildKit `SecretsUsedInArgOrEnv` warning is gone. +- Tower rebuild completed and the previous Docker BuildKit `SecretsUsedInArgOrEnv` warning no longer appears. Limitations: - The start script still has safe local defaults for standalone/dev startup. Shared deployments should set `GEOINTEL_POSTGRES_PASSWORD` via runtime configuration.