Supabase Containers Exclusion

[iamhectorsosa]

In the scripts we are excluding some of the containers during development. It would be great to determine which containers are needed and explain it in the docs.

Containers are related to Supabase and its various components.

Here is a description for each of the containers:

• gotrue: This container is responsible for handling authentication and user management in Supabase. It is part of the GoTrue project, which is an open-source authentication server built on top of PostgreSQL
• realtime: This container is related to the Realtime component of Supabase, which provides real-time functionality for your application. It is built using Elixir and allows you to listen to PostgreSQL inserts, updates, and deletes using websockets
• storage-api: This container is responsible for handling the storage functionality in Supabase. It is part of the Supabase Storage API, which allows you to store and manage files and assets for your application
• imgproxy: This container is used for image processing in Supabase. It is part of the Imgproxy project, which is an open-source, high-performance, and scalable standalone proxy for image manipulation
• kong: This container is related to the Kong API Gateway, which is used in Supabase to manage and route API requests. Kong is a cloud-native API gateway that provides features like authentication, rate limiting, and more
• inbucket: This container is part of the Supabase Storage API and is used for handling file uploads and downloads. It is built on top of the Inbucket project, which is an open-source file server with support for Amazon S3 and Google Cloud Storage
• postgrest: This container is responsible for providing a RESTful API for your PostgreSQL database. It is part of the PostgREST project, which is an open-source web server that turns your PostgreSQL database directly into a RESTful API
• pgadmin-schema-diff: This container is related to the pgAdmin tool, which is a web-based PostgreSQL administration and management tool. The schema-diff feature allows you to compare and synchronize database schemas between different PostgreSQL instances
• migra: This container is part of the Supabase Migration system, which allows you to manage database migrations and updates. It is built using the Migrate tool, which is an open-source database migration tool for PostgreSQL
• postgres-meta: This container is related to the PostgreSQL database used in Supabase. It is responsible for managing the metadata and schema of the database
• studio: This container is part of the Supabase Studio, which is a web-based interface for managing your Supabase project. It provides features like database management, real-time monitoring, and more
• edge-runtime: This container is responsible for handling Supabase Edge Functions, which are serverless functions that run close to your database and can be triggered by database events or HTTP requests
• logflare: This container is related to the Logflare service, which is used for logging and monitoring in Supabase. It allows you to collect, analyze, and visualize logs from your application
• vector: This container is part of the Vector project, which is an open-source data processing engine for building observability pipelines. It is used in Supabase for log processing and analysis
• pgbouncer: This container is related to the PgBouncer project, which is a connection pooler for PostgreSQL. It is used in Supabase to manage and optimize database connections
• pg_prove: This container is part of the pg_prove project, which is a tool for testing PostgreSQL databases. It is used in Supabase for testing and validating database schema and queries

Ref: https://supabase.com/docs/guides/self-hosting/docker#architecture