My coworker just bumped into an issue with his local supabase volumes getting corrupted somehow. In order to solve this we had to stop supabase, manually tear down the docker volumes, and restart to get things working again.
There was no easy way to supabase stop --rm (like a docker compose down --rm). A destructive option for supabase stop would be valuable in these instances.
To Reproduce
Steps to reproduce the behavior:
Deliberately screw up your docker volumes (Exercise left for the reader)
Describe the bug
My coworker just bumped into an issue with his local supabase volumes getting corrupted somehow. In order to solve this we had to stop supabase, manually tear down the docker volumes, and restart to get things working again.
There was no easy way to
supabase stop --rm
(like adocker compose down --rm
). A destructive option forsupabase stop
would be valuable in these instances.To Reproduce
Steps to reproduce the behavior:
Expected behavior
supabase stop --rm
or similar.Screenshots
N/A
System information
Irrelevant
Additional context
N/A