Part 4 — The first Supabase instance

Part 4 of 7 — Self-hosting Supabase: a learning journey We have a server, Docker Swarm, and Traefik running. Now we deploy Supabase. This is the part with the most surprises. I will document each one as we get to it. What one Supabase project is Before writing any configuration, it helps to have a clear picture of what we are deploying. One Supabase project is eight Docker services: Internet | Traefik (TLS termination, routing) | Kong (API gateway, port 8000) | +-- GoTrue (auth, port 9999) +-- PostgREST (REST API, port 3000) +-- Realtime (WebSockets, port 4000) +-- Storage (files, port 5000) +-- Studio (dashboard, port 3000) +-- postgres-meta (schema introspection, port 8080) PostgreSQL (port 5432, internal only) Kong is the only service accessible from the internet (through Traefik). All others are on an internal Docker overlay network. PostgreSQL is never published to the host. The secrets you need to generate Before writing the compose file, generate these values: # Postgres passwor