chore(docker): faunosteo_ naming convention for Docker resources (compose project + container), documented CLI limit

This commit is contained in:
bchanot committed 2026-10-09 16:26:06 +02:00
1 parent 584b165bfa
commit 6c5b2b7754
6 files changed
+58 -1

No files matched your search

+6
View File
@@ -66,6 +66,12 @@ Local endpoints (`config.toml`):
`pnpm db:start` prints the `anon` and `service_role` keys. Only the anon key
ever reaches the browser.
Containers, volumes and network are named `supabase_<service>_faunosteo`
(`project_id` of `config.toml`): the CLI imposes this pattern, so the
`faunosteo_` prefix convention of DEPLOY.md ("Docker resource naming")
applies as a suffix here. Several projects can run side by side as long as
their `project_id` and ports differ.
Two kinds of seed (`config.toml [db.seed] sql_paths`):
| File | Scope | Content |