fix(cuprate): avoid Penpot RPC port collision

This commit is contained in:
archipelago
2026-08-23 01:43:09 -04:00
parent f1b5d2d267
commit 37a82fd2f9
2 changed files with 8 additions and 6 deletions
+5 -4
View File
@@ -83,9 +83,10 @@ app:
# what wallets use when connecting to a "remote node". Disabled by # what wallets use when connecting to a "remote node". Disabled by
# cuprated's own default; enabled via files[] below. A dashboard login # cuprated's own default; enabled via files[] below. A dashboard login
# would break wallet clients connecting programmatically, same # would break wallet clients connecting programmatically, same
# reasoning as electrumx's port — canonical port 18089 is free on this # reasoning as electrumx's port. The daemon still uses its canonical
# fleet, so no remap needed here. # container port 18089, but Penpot already owns host port 18089, so this
- host: 18089 # maps the public host port to the free 18090 instead.
- host: 18090
container: 18089 container: 18089
protocol: tcp protocol: tcp
auth: none auth: none
@@ -136,7 +137,7 @@ app:
health_check: health_check:
type: tcp type: tcp
# Restricted RPC — the only RPC surface published now. # Restricted RPC — the only RPC surface published now.
endpoint: localhost:18089 endpoint: localhost:18090
interval: 30s interval: 30s
timeout: 5s timeout: 5s
retries: 3 retries: 3
+3 -2
View File
@@ -1746,9 +1746,10 @@ app:
} }
} }
exempt.sort(); exempt.sort();
// 28 as of 2026-08-21: the 26 below plus cuprate's two exemptions — // 28 as of 2026-08-23: the 26 below plus cuprate's two exemptions —
// 18183 (Monero p2p gossip, same reasoning as bitcoin's 8333) and // 18183 (Monero p2p gossip, same reasoning as bitcoin's 8333) and
// 18089 (Monero restricted RPC, upstream's own safe-for-public // 18090 (host mapping for Monero's canonical 18089 restricted RPC,
// upstream's own safe-for-public
// subset that wallets connect to directly as a "remote node" over // subset that wallets connect to directly as a "remote node" over
// plain HTTP JSON-RPC — same reasoning as electrumx's 50001). // plain HTTP JSON-RPC — same reasoning as electrumx's 50001).
// cuprate's unrestricted RPC (full node control) stays loopback-only // cuprate's unrestricted RPC (full node control) stays loopback-only