search

supabase / cli

Supabase CLI. Manage postgres migrations, run Supabase locally, deploy edge functions. Postgres backups. Generating types from your database schema.
https://supabase.com/docs/reference/cli/about
MIT License
1.02k stars 201 forks source link

Allow enabling/disabling all services in the config.toml configuration #1988

Closed daniel-j-h closed 7 months ago

daniel-j-h commented 7 months ago

At the moment the supabase/config.toml allows us to disable some services e.g.

[realtime]
enabled = false

https://github.com/supabase/cli/blob/6eee42fe379c9199172a92604e66b4cfed2b0721/internal/utils/templates/init_config.toml

but it looks like some services are not configurable in the config file: for example by default it looks like the imgproxy and edge-runtime services are always getting started (i.e. their containers are started) on supabase start.

It seems like there is an exclude flag in the supabase start sub-command to disable them manually

supabase start --exclude 'imgproxy,edge-runtime'

https://github.com/supabase/cli/blob/6eee42fe379c9199172a92604e66b4cfed2b0721/docs/supabase/start.md

Is this by design or an oversight?

Should there be sections in the config file supabase init creates and all other commands respect, such as

[imgproxy]
enabled = false

[edgeruntime]
enabled = false

Then we no longer have to enable/disable some services in the config and some on the command line via exclude flag.

System information

sweatybridge commented 7 months ago

closing as a duplicate of https://github.com/supabase/cli/issues/1414