fix(workspace): LAN exposure via host firewall — the Supabase CLI forces 0.0.0.0, so PostgreSQL / Studio / raw Mailpit close by UFW rules on the LAN interface; gateway reduced to Mailpit behind basic auth on 54325
Owner run: the CLI prints 'All services bind to 0.0.0.0' and ignored the rootless daemon's default address; the gateway could not share 54321/54324 with 0.0.0.0 listeners. Now: Kong serves the API directly; the DEV gateway serves only Mailpit with basic auth on <DEV host>:54325; ENVIRONMENTS.md §3 gives the exact UFW rules (interface-scoped deny on 54322-54324, two cases by current UFW state), rollback and impact; dev:net-check proves the allowed surfaces from a distinct Docker network (5/5 OK) and prints the refusal checks to run from another device, since a rootless container's traffic to the host is delivered locally and cannot see the LAN firewall. LRN-053 corrects LRN-052.
This commit is contained in:
1 parent
a8edd59059
commit
e633169a00
11 files changed
+143
-111
No files matched your search
@@ -2,9 +2,9 @@
|
||||
# DEV gateway on the private network (docs/development/ENVIRONMENTS.md §3).
|
||||
# pnpm dev:gateway # up: generates the Mailpit credentials once, starts faunosteo_dev_gateway
|
||||
# pnpm dev:gateway:stop # down
|
||||
# Prerequisite: the rootless Docker daemon binds published ports on loopback by default
|
||||
# (~/.config/docker/daemon.json {"ip": "127.0.0.1"}, ENVIRONMENTS.md §3.1), so the
|
||||
# gateway is the only listener of the stack on the LAN address.
|
||||
# Serves Mailpit behind basic auth on <FAUNOSTEO_DEV_HOST>:54325; the raw ports the
|
||||
# Supabase CLI publishes on 0.0.0.0 (54322 PostgreSQL, 54323 Studio, 54324 Mailpit) are
|
||||
# closed to the LAN by the host firewall rules of ENVIRONMENTS.md §3.2.
|
||||
set -euo pipefail
|
||||
cd "$(dirname "$0")/.."
|
||||
. scripts/dev-env.sh
|
||||
|
||||
Reference in new issue
Block a user