github-such-software/adaptive-multi-protocol-gateway
1
0
Fork 0
mirror of https://github.com/Such-Software/adaptive-multi-protocol-gateway.git synced 2026-10-17 15:41:41 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add address capture to activation plan

Browse Source
This commit is contained in:
jwinterm
2026-07-06 10:30:42 -04:00
parent bf2a171ec6
commit 12983ca134
9 changed files with 169 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture.md
+3 -2
View File
@@ -111,7 +111,8 @@ render-only environment while making daemon ownership decisions explicit.
`ampg apply --dry-run` turns daemon status and generated config artifacts into an ordered
activation sequence. Each enabled protocol gets output, artifact, daemon, and health
steps. Blocked steps stop the command before any live apply path can touch services.
steps, plus an address step when AMPG must capture or confirm a generated transport
identity. Blocked steps stop the command before any live apply path can touch services.
The dry-run command is intentionally stricter than `doctor`: missing generated output is
blocked during activation, because AMPG must not point a transport at an unbuilt output
@@ -126,7 +127,7 @@ future live apply support.
With `--write-artifacts`, install-plan writes managed config and supervisor files under
the configured `plan_root`; those files are review artifacts, not installed service
state.
state. Generated managed-daemon configs point runtime state at `gateway.state_dir`.
Tor and I2P HTTP publishing include the transport daemon and the loopback web-serving
layer in the install plan, because the hidden service or tunnel must have a local HTTP
docs/configuration.md
+2 -2
View File
@@ -112,8 +112,8 @@ workflow.
`[gateway]` paths are resolved relative to `gateway.toml` when they are not absolute.
`state_dir`
: AMPG-owned durable state. Managed daemon identities, generated transport state, and
the captured address registry live here.
: AMPG-owned durable state. Managed daemon identities, generated transport state, daemon
logs, daemon-written addresses, and the captured address registry live here.
`cache_dir`
: Rebuildable intermediate data.
docs/daemon-management.md
+6 -5
View File
@@ -66,7 +66,8 @@ blocked.
`install-plan --write-artifacts` writes managed daemon configs and platform supervisor
files under the configured `plan_root`, grouped by site, protocol, and platform. For
Tor/I2P HTTP publishing, AMPG writes both transport-daemon artifacts and loopback nginx
artifacts.
artifacts. The generated daemon configs store runtime state, identity keys, logs, and
daemon-written addresses under `gateway.state_dir`.
`addresses list` prints the effective public address for each enabled protocol:
configured, captured, derived, or placeholder. `addresses capture` reads daemon-written
@@ -78,10 +79,10 @@ target real transport URLs; preview checks target local loopback preview endpoin
Missing output blocks the plan, while placeholder transport addresses are review items.
`apply --dry-run` prints the activation sequence for each enabled protocol: generated
output readiness, config artifacts to review, daemon action, and post-apply health
checks. It exits nonzero when any step is blocked. `--write-artifacts` writes reviewable
config snippets to the configured plan root but still does not install or reload
services.
output readiness, config artifacts to review, daemon action, address capture or reuse,
and post-apply health checks. It exits nonzero when any step is blocked. `--write-artifacts`
writes reviewable config snippets to the configured plan root but still does not install
or reload services.
`--protocol` scopes operational commands to selected enabled protocols. A clearnet
`adopt` failure will block a full activation run, but it will not block