feat(deploy): define isolated managed test target

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-10 08:42:41 +03:00
1 parent 0b4b909a20
commit c5cabf076f
9 files changed
+159 -10

No files matched your search

+5 -3
View File
@@ -27,7 +27,7 @@ deliberately forging a provisioned runtime.
The managed `config` is a standalone **full config only in this fresh volume**.
Never replace, adopt, or symlink over `/opt/zapret2/config` or any existing
service config. Future provisioning/entrypoint must ensure the base daemon
service config. The new deployment entrypoint must ensure the base daemon
actually honors the exact `ZAPRET_CONFIG` path; compatibility remains unproven.
Existing services would require a separately designed managed **include
fragment**, not this full-config adapter. No such integration is implemented.
@@ -84,8 +84,10 @@ Directories must not be writable by untrusted processes; hostile concurrent
filesystem mutation is outside the transaction boundary. Shell config safety
and exact GGC filtering are unchanged.
No Docker socket, deployment/container/remote changes, old target paths, Xray
edits, monitor loop or host firewall provisioning are included. Before deployment,
The isolated [Compose definition](deploy/managed-target/README.md) now supplies
the marker, mount and ordered startup; it has not been built or deployed.
No Docker socket, remote/container operations, old target paths, Xray edits,
monitor loop or host firewall provisioning are included. Before deployment,
provisioning must verify the pinned image honors `ZAPRET_CONFIG`, supports all
listed variables, and starts ss-local while the baseline leaves nfqws2 disabled.
Start the fresh target with that baseline, then verify active apply installs