mirror of
https://github.com/Such-Software/adaptive-multi-protocol-gateway.git
synced 2026-10-17 07:31:32 +02:00
74 lines
2.3 KiB
Markdown
74 lines
2.3 KiB
Markdown
# Generated Daemon Adapters
|
|
|
|
> Status: generated | Updated by `python3 -m ampg docs generate` | Applies to: AMPG
|
|
|
|
This file is generated from code. Do not edit it by hand.
|
|
|
|
|
|
## nginx
|
|
|
|
- Protocols: clearnet, tor, i2p
|
|
- Default policy: `adopt`
|
|
- Generated artifacts: server block snippets
|
|
- Provider sources: `configured`, `system-adopted`, `system-managed`, `platform-package`
|
|
|
|
Notes:
|
|
- Clearnet defaults to adopt because TLS and public vhost policy are operator-owned.
|
|
- Tor/I2P HTTP targets can use loopback-only server blocks.
|
|
|
|
## tor
|
|
|
|
- Protocols: tor
|
|
- Default policy: `auto`
|
|
- Generated artifacts: torrc hidden-service snippet
|
|
- Provider sources: `configured`, `bundled-sidecar`, `system-adopted`, `system-managed`, `platform-package`
|
|
|
|
Notes:
|
|
- AMPG should preserve existing HiddenServiceDir material when adopting.
|
|
- Managed hidden-service keys belong under AMPG state.
|
|
|
|
## i2pd
|
|
|
|
- Protocols: i2p
|
|
- Default policy: `auto`
|
|
- Generated artifacts: i2pd server tunnel snippet
|
|
- Provider sources: `configured`, `bundled-sidecar`, `system-adopted`, `system-managed`, `platform-package`
|
|
|
|
Notes:
|
|
- Web tunnels should use web-specific key files.
|
|
- Existing RPC/P2P tunnel keys are not reused for web publishing.
|
|
|
|
## agate
|
|
|
|
- Protocols: gemini
|
|
- Default policy: `auto`
|
|
- Generated artifacts: Agate plan values
|
|
- Provider sources: `configured`, `bundled-sidecar`, `system-adopted`, `system-managed`, `platform-package`
|
|
|
|
Notes:
|
|
- Gemini serves generated Gemtext output directly.
|
|
- Certificate and key paths are plan values until install/apply support exists.
|
|
|
|
## ipfs
|
|
|
|
- Protocols: ipfs
|
|
- Default policy: `auto`
|
|
- Generated artifacts: fixture manifest route expectations
|
|
- Provider sources: `configured`, `bundled-sidecar`, `system-adopted`, `system-managed`, `platform-package`
|
|
|
|
Notes:
|
|
- IPFS output is static web content for a local gateway or later pinning.
|
|
- IPFS is content-addressed distribution, not an anonymity layer.
|
|
|
|
## rnsd
|
|
|
|
- Protocols: reticulum
|
|
- Default policy: `auto`
|
|
- Generated artifacts: Reticulum page-service plan
|
|
- Provider sources: `configured`, `bundled-sidecar`, `system-adopted`, `system-managed`, `platform-package`, `operator-interface`
|
|
|
|
Notes:
|
|
- Reticulum output is planned as small page-service content.
|
|
- Reticulum is resilient/private routing, not an anonymity layer.
|
|
- Physical interfaces may require explicit operator setup.
|