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.07k stars 209 forks source link

Supabase stop is remove but not stop all containers #2079

Closed jingsam closed 7 months ago

jingsam commented 7 months ago

Link Add a link to the page which needs improvement (if relevant)

Describe the problem supabase stop is actually remove all local Supabase containers, not stop them. This is different. Like docker stop and docker rm, stop means the containers still exist and we can restart them again, rm means the containers is gone and we should recreate again.

Describe the improvement A clear and concise description of the improvement.

Additional context Add any other context or screenshots that help clarify your question.

sweatybridge commented 7 months ago

Could you describe a use case for leaving the containers after supabase stop? I know users with multiple local projects find it confusing to have stopped containers show up in docker ls.

Perhaps it's worth clarifying that the goal of our CLI is not to provide the same interface as docker/kube commands. We don't want to confuse users with the semantic differences between stop, down, apply, etc. If users need that level of control, they can always use the native docker commands instead.

The primary goal of CLI is to give users a single way to start and stop the local development stack.