Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to restart supabase services when I changed config.toml #2078

Open
jingsam opened this issue Mar 22, 2024 · 3 comments
Open

How to restart supabase services when I changed config.toml #2078

jingsam opened this issue Mar 22, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@jingsam
Copy link

jingsam commented Mar 22, 2024

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

Describe the problem
When I enable analytics service in config.toml, how can I make supabase cli start service?
Maybe I can do with supabase stop and supabase start, but that would be recreate all service which is slow. Maybe an restart command like docker restart is quicker?

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
Copy link
Contributor

Thanks for the suggestion. I think we can have supabase start compare the list of running services vs enabled services in config.toml. It can then launch newly enabled containers incrementally.

@jingsam
Copy link
Author

jingsam commented Mar 22, 2024

Thanks for the suggestion. I think we can have supabase start compare the list of running services vs enabled services in config.toml. It can then launch newly enabled containers incrementally.

Yes, just like k8s kubetcl apply config.yml, autodiff and action to keep local services status match the config.toml

@zhanziyang
Copy link

+1 for this

@sweatybridge sweatybridge added the enhancement New feature or request label Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants