The owner tests from other devices of the private network: every test surface is addressed by the machine's LAN address, never 127.0.0.1 or localhost, never hard-coded. scripts/dev-env.sh decides the host once (hostname -I, FAUNOSTEO_DEV_HOST override, production hosts refused); scripts/supabase.sh exports it for every CLI call (pnpm db:*, pnpm supabase) because config.toml now reads api.external_url (mail links), auth.site_url and studio.api_url with env(); scripts/dev.sh = pnpm dev on that origin, pnpm dev:offline keeps the local tool alone; dev-lan.sh removed. Verified: GoTrue API_EXTERNAL_URL and Studio SUPABASE_PUBLIC_URL on the LAN address, a signup mail linking to http://<lan>:54321/auth/v1/verify, the four published ports answering from a separate Docker network, and the 10-step procedure in headless Chromium at the LAN origin with every request URL audited (no 127.0.0.1 / localhost).
11 lines
511 B
Bash
Executable File
11 lines
511 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# Supabase CLI with the DEV origin exported: supabase/config.toml reads the
|
|
# API external URL, the site URL and Studio's API URL through env(), so every
|
|
# CLI call (start, stop, status, db reset, test db, gen types) must see them,
|
|
# or the literal "env(...)" text lands in the running services.
|
|
# pnpm supabase <args> · pnpm db:start · FAUNOSTEO_DEV_HOST=10.0.0.5 pnpm db:start
|
|
set -euo pipefail
|
|
cd "$(dirname "$0")/.."
|
|
. scripts/dev-env.sh
|
|
exec node_modules/.bin/supabase "$@"
|