adaptive-multi-protocol-gateway/docs/generated/daemon-adapters.md

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

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

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

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

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

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

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.