Supabase (self-hosted, core)

Qué obtienes

• Los 7 servicios aprovisionados juntos: supabase-db, supabase-auth, supabase-rest, supabase-realtime, supabase-storage, supabase-meta, supabase-studio
• Una plantilla comunitaria, aún no verificada de extremo a extremo por el equipo de Railyard
• HTTPS automático y despliegues sin downtime

Cómo desplegar Supabase (self-hosted, core)

1. 1

   Conecta un servidor

   Conecta un servidor de DigitalOcean, Hetzner o Vultr a Railyard, o cualquier servidor Linux por SSH.

2. 2

   Haz clic en "Desplegar Supabase (self-hosted, core)"

   Railyard construye el contenedor y aprovisiona los 7 servicios.

3. 3

   Configura tu dominio

   Apunta tu dominio a la app. Railyard emite un certificado HTTPS y lo renueva automáticamente.

Por qué desplegar en Railyard

Railyard aprovisiona los 7 servicios de este stack juntos — supabase-db, supabase-auth, supabase-rest, supabase-realtime, supabase-storage, supabase-meta, supabase-studio — conectados para hablarse por la red privada, en un servidor que ya pagas.

Desplegar Supabase (self-hosted, core) es una pieza de un stack más grande que puedes seguir construyendo — agrega una base de datos, un worker, un cache, u otra app, todo en los mismos servidores que ya pagas.

Ideal para

• A self-hosted Postgres + Auth + Storage + Realtime backend
• A Firebase-style backend for a team that wants to own the database

Bueno saber

• Every service gets its own Railyard URL instead of sitting behind one API gateway — Supabase's own compose routes everything through Kong/Envoy, which is skipped here the way nginx is skipped elsewhere in this catalog
• This runs as a single project, same as upstream self-hosted Supabase — Studio doesn't support multiple organizations or projects the way Supabase Cloud does
• Known gap: supabase-realtime still won't boot cleanly — its migrator writes an unqualified public.schema_migrations, which collides with the bookkeeping table the supabase/postgres image's own bootstrap already creates there. Upstream avoids this by mounting an extra init script that pre-creates a dedicated _realtime schema before Realtime ever starts; this template has no equivalent bootstrap step yet, so redirecting Realtime's search_path there fails too (the schema doesn't exist). Needs a Railyard-side way to run one-time setup SQL against supabase-db before dependent services boot

Preguntas frecuentes

Plantillas relacionadas