feat(runtime): bound recovery and add safe release supervision
Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
780ca71e17
commit
b1e458a0a5
16 files changed
+941
-66
No files matched your search
@@ -2,6 +2,24 @@
|
||||
|
||||
Go CLI for scanning and checking YouTube TLS bypass strategies with `blockcheckw`.
|
||||
|
||||
## Production preparation (acceptance pending)
|
||||
|
||||
The standalone deployment candidate is a **new isolated target**, never an
|
||||
upgrade/adoption of an existing zapret or Xray service. The legacy `managed-test`
|
||||
role and fixed identity guards remain intentional, including for prod-like runs.
|
||||
See [release, configuration, upgrade and rollback guidance](MANAGED_TARGET.md#production-preparation)
|
||||
and the [deployment/service instructions](deploy/managed-target/README.md).
|
||||
Pinned builds and supervision are preparation, not production acceptance: real
|
||||
restart/deadline tests and end-to-end target validation remain rollout gates.
|
||||
Select an immutable managed-target digest with `ZAPRET_AUTOTUNE_IMAGE` in the
|
||||
private deployment `.env`; tags/local defaults are only build/test candidates.
|
||||
Bootstrap/recovery shares a 90-minute whole-job deadline plus a separate 30-second
|
||||
restoration reserve, an abnormal ceiling rather than normal candidate failure.
|
||||
Timeout exit 75 requires clean timeout/cancellation only; cleanup/safety errors
|
||||
veto retry. Optional foreground systemd uses `Restart=no` plus forced exit-75
|
||||
restart, limited to three starts per six hours; Compose stop grace is 120s and
|
||||
systemd stop timeout 180s.
|
||||
|
||||
## Manual managed-test activation (not deployed)
|
||||
|
||||
`managed init|status|active-ids|apply` requires exact role `managed-test`, target ID
|
||||
@@ -20,7 +38,7 @@ group, fixed target init executable and explicit runtime-config
|
||||
binding. It uses full target-local firewall/daemon restart and Player API post-check, with
|
||||
atomic rollback on failure. See [MANAGED_TARGET.md](MANAGED_TARGET.md) for guards
|
||||
and provisioning prerequisites. An isolated pinned deployment definition is in
|
||||
[deploy/managed-target](deploy/managed-target/README.md); build/run are deferred.
|
||||
[deploy/managed-target](deploy/managed-target/README.md); acceptance remains pending.
|
||||
An injected bootstrap/saved-first recovery adapter now connects the persisted
|
||||
monitor foundation to blockcheck, immutable candidates and transactional apply.
|
||||
`managed monitor` and the dedicated target entrypoint now wire these adapters;
|
||||
|
||||
Reference in new issue
Block a user