# supabase

The `supabase` module of the mesh catalogue: runs the container image `timberio/vector`; runs the container image `supabase/postgres`; runs the container image `supabase/logflare`; runs the container image `kong`; runs the container image `supabase/gotrue`; runs the container image `postgrest/postgrest`; runs the container image `supabase/realtime`; runs the container image `darthsim/imgproxy`; runs the container image `supabase/storage-api`; runs the container image `supabase/postgres-meta`; runs the container image `supabase/edge-runtime`; runs the container image `supabase/studio`; runs the container image `supabase/supavisor`.

## Files it does not know

Each directory or archive this module declares says how it treats a file it did not write (ADR 0422, ADR 0416).

- `${dir:state}`: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).
- `${dir:state}/db-init`: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).
- `${dir:state}/functions-main`: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).
- `${dir:db-data}`: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).
- `${dir:state}/dumps`: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).
- `${dir:db-config}`: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).
- `${dir:storage}`: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).
- `${dir:functions}`: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).