docs: converge operator guidance on tht
This commit is contained in:
@@ -142,7 +142,7 @@ the teardown if any container, volume, or network has a foreign run label.
|
||||
|
||||
```sh
|
||||
bash scripts/unified-deployment-smoke.sh
|
||||
bash scripts/thothctl-update-smoke.sh
|
||||
bash scripts/tht-update-smoke.sh
|
||||
bash scripts/server-deployment-smoke.sh
|
||||
```
|
||||
|
||||
@@ -151,10 +151,10 @@ registry, recreates with the Git remote offline, activates a valid Git update, r
|
||||
content while retaining the valid snapshot, and checks the four persistence volumes. The unified
|
||||
and update-only smokes
|
||||
inject a digest-pinned non-core candidate under a deliberately mismatched Pi version and require
|
||||
`thothctl pi update` to roll back while preserving settings, sessions, Pi state, registry revision,
|
||||
`tht pi update` to roll back while preserving settings, sessions, Pi state, registry revision,
|
||||
and mount identity. The rollback candidate is the digest-pinned `hello-world` executable: a
|
||||
preflight proves that it exits successfully, so the failed replacement core satisfies
|
||||
`thothctl`'s stopped-core compensation precondition. The server smoke uses the same smoke-built
|
||||
`tht`'s stopped-core compensation precondition. The server smoke uses the same smoke-built
|
||||
core/frontend images with the server and required session overlays, disposable bind roots and
|
||||
secret files, upstream-auth checks, and a fail-closed `503` assertion for its deliberately
|
||||
unavailable disposable session endpoint. No real provider, database credential, or repository
|
||||
@@ -190,7 +190,7 @@ The deterministic native Windows contract is:
|
||||
```
|
||||
|
||||
It checks Git's CRLF/LF attributes and bytes, copies tracked source into a temporary path containing
|
||||
spaces, builds and invokes native Windows `thothctl` there, and renders exactly `core` plus
|
||||
spaces, builds and invokes native Windows `tht` there, and renders exactly `core` plus
|
||||
`frontend` without starting containers. On a supported self-hosted Windows Docker Desktop/WSL2
|
||||
runner, dispatch the deployment workflow with `windows_docker_startup=true`; that job executes:
|
||||
|
||||
@@ -198,7 +198,7 @@ runner, dispatch the deployment workflow with `windows_docker_startup=true`; tha
|
||||
.\scripts\test-windows-clone-contract.ps1 -DockerStartup
|
||||
```
|
||||
|
||||
Startup mode adds bounded image build/two-service health startup, installation-aware `thothctl`
|
||||
Startup mode adds bounded image build/two-service health startup, installation-aware `tht`
|
||||
status, stopped-container-aware ownership checks, and exact cleanup. The ordinary hosted Windows
|
||||
job remains deterministic and does not claim Docker startup.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user