Merge: t-paliad-151 Phase A.5 — env-var passthrough for Paliadin remote-routing
Drops the original network_mode: host approach (incompatible with Dokploy's compose-network injection) in favour of a far simpler discovery: docker bridge + mLake's host-side tailscale0 + Docker NAT already routes container outbound to mRiver:22022. Source IP NAT'd to mLake's tailnet IP, matches the from=100.99.98.201 clause on mRiver's authorized_keys. Compose change is therefore JUST the 5 PALIADIN_* env entries pulled through from already-registered Dokploy secrets. No traefik conflict. Phase A.5 verified empirically before this merge (2026-05-08 11:23): plain alpine container on Dokploy's default bridge SSHs to mriver:22022 via the paliadin-shim and gets "ok" in ~3s. Refs m/paliad#12
This commit is contained in:
@@ -20,5 +20,19 @@ services:
|
||||
- SMTP_FROM=${SMTP_FROM}
|
||||
- SMTP_FROM_NAME=${SMTP_FROM_NAME}
|
||||
- SMTP_USE_TLS=${SMTP_USE_TLS}
|
||||
# Paliadin remote routing (t-paliad-151). When PALIADIN_REMOTE_HOST
|
||||
# is set, paliad forwards each turn to mRiver via SSH on port 22022.
|
||||
# The container reaches mRiver over Tailscale via mLake's host-side
|
||||
# tailscale0 + Docker source NAT — no network_mode override needed
|
||||
# (verified Phase A.5: a plain alpine container on Dokploy's
|
||||
# default bridge SSHs to mriver:22022 in 3 s, source IP NAT'd to
|
||||
# mLake's tailnet IP, matches the from="100.99.98.201" clause on
|
||||
# mRiver's authorized_keys).
|
||||
# PRIVATE_KEY and KNOWN_HOSTS are multi-line Dokploy secrets.
|
||||
- PALIADIN_REMOTE_HOST=${PALIADIN_REMOTE_HOST}
|
||||
- PALIADIN_REMOTE_PORT=${PALIADIN_REMOTE_PORT}
|
||||
- PALIADIN_REMOTE_USER=${PALIADIN_REMOTE_USER}
|
||||
- PALIADIN_SSH_PRIVATE_KEY=${PALIADIN_SSH_PRIVATE_KEY}
|
||||
- PALIADIN_KNOWN_HOSTS=${PALIADIN_KNOWN_HOSTS}
|
||||
# - ANTHROPIC_API_KEY=${ANTHROPIC_API_KEY} # Phase H (AI Frist-Extraktion), currently deferred
|
||||
restart: unless-stopped
|
||||
|
||||
Reference in New Issue
Block a user