Prepare containerized dev/prod deployment (inactive)
Add a Docker image and separate Compose projects for development and production, based on the stable main behaviour without the privacy gateway. Nothing is wired into the existing systemd deploy workflow. - One non-root image (api | ui | preflight), base image pinned by digest, dependencies from a hash-locked universal lock without torch and sentence-transformers (MiniLM is not on the runtime path) - Preflight aborts on: VECTOR_DIM != 768 or non-nomic embedding profile, implicit or cross-env collection prefix, cloud keys without explicit egress acknowledgement, missing/empty or writable vault mount - Vault is a read-only NAS bind mount without host-path autocreation; healthcheck turns unhealthy when the vault sentinel disappears - Dev runs its own Qdrant; prod reuses the existing host instance - API published on loopback only; read-only rootfs, cap_drop ALL, no-new-privileges - Dev workflow kept as an inactive template outside .gitea/workflows - Docs: operations guide and migration plan with release gates, test baseline classification, R2/R3 and privacy gateway requirements Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
0d61a9e191
commit
7a225ba2b6
18 files changed
+2864
No files matched your search
@@ -0,0 +1,2 @@
|
||||
-c requirements.lock
|
||||
pytest>=8.4.2
|
||||
Reference in new issue
Block a user