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

+24
View File
@@ -21,6 +21,30 @@ The host should publish only ports `22`, `80`, `443` to the internet. The
container port (`8080` by default) should stay loopback-only — the host
reverse proxy reads from it on `127.0.0.1:8080`.
### Docker resource naming
Several SaaS may share one VPS, so every Docker resource Faunosteo owns
carries the `faunosteo_` prefix whenever its name is configurable:
containers, Compose project (hence networks and named volumes), images and
future services (`faunosteo_app`, `faunosteo_worker`, `faunosteo_supabase_db`…).
| Resource | Name | Set by |
| ------------------------------ | ------------------------------------- | ---------------------------------------- |
| SPA container | `faunosteo_app` | `container_name` in `docker-compose.yml` |
| Compose project, network | `faunosteo`, `faunosteo_default` | top-level `name:` in `docker-compose.yml` |
| Local Supabase stack (CLI) | `supabase_<service>_faunosteo` | `project_id` in `supabase/config.toml` |
Known limit: the Supabase CLI hard-codes `supabase_<service>_<project_id>`
for its containers, volumes and network (`supabase_network_faunosteo`); the
project id is a suffix, not a prefix. The name stays unique per SaaS, so no
workaround is applied. A self-hosted production Supabase (docs/development/
SUPABASE.md §10) is a Compose project we write ourselves and must follow the
prefix (`faunosteo_supabase_db`, `faunosteo_supabase_auth`, …).
Renaming a container never touches data: the SPA container holds no volume.
When a future service gains a named volume, keep the volume name across a
rename (`external: true` or an explicit `name:`) instead of recreating it.
---
## Required environment