🔥
Mar 10 (edited) • Supabase
How I reconfigured the project to run everything with one command
Hello engineers,
I was annoyed that I needed to run two separate commands to start the whole app. So, I did some research, asked an LLM, and found a great solution! :)
Instead of running the Supabase backend via the CLI, I updated the main Docker Compose file to include all Supabase containers directly. Now, I can just run npm start in the root directory, and the entire project, frontend and backend. Everything starts at the same time.
What I did:
- Completely restructured the server directory (following this documentation and this repository)
- Ensured all volumes for the backend containers are stored in the server directory.
Services I added:
- studio
- kong
- auth
- rest
- realtime
- storage
- imgproxy
- meta
- functions
- analytics
- db
- supavisor
Volumes I added:
- db-config
- deno-cache
Now I can run the entire stack with just one command! :)
Gitlab commit link
Do you want to do a code review?
2
0 comments
How I reconfigured the project to run everything with one command
powered by
skool.com/szykulatech-3240
We focus on JS/TS, React, Next.js, Supabase, shadcn/ui, Tailwind CSS, and deployments on Netlify. We focus on fast learning.
Suggested communities
Powered by