Is there any way to split my project into 2 types (phases) - In one place I would develop and modify the web application, and in the other place I would deploy the live version. What I mean.
I have a frontend (WeWeb) and a backend (Supabase). But as I understand it, the current frontend is only connected to one version of Supabase - the working/live version. To test the updates I will develop in frontend and backend, I need to make another version of backend (Supabase) ? How to do it properly so as not to affect the live version while I develop the updates ? Please share your experience, how do you divide your web application into development environment and uploaded version ? It’s important to me that development doesn’t interfere with the live version. Is it possible to quickly update the live version from the version I am developing? Any advice would be appreciated!
Yes, it’s definitely possible and a good idea to split your project into two environments, one for development and one for production. Most teams and any experienced web application development company usually set up a staging or dev environment that closely matches the live setup. In your case with Supabase, you can create a second project that works as your development backend. Then connect your WeWeb frontend to this dev Supabase project while you work on updates. This keeps your live version safe from any testing or changes. Once you’re happy with the updates, you can apply the changes to the live Supabase manually and reconnect the frontend. It takes a little extra effort, but it helps avoid issues and gives you a safer way to build and test.