![]() ![]() Work offline: Need to work from a train? A plane? An automobile? No problem. If you follow these local development practices, you'll store all of your table schemas in code. But what if you need more than two? When you develop locally, you can spin up unlimited local projects and link them with live projects when you're ready to launch.Ĭonfiguration in code: If you directly change your tables via the Dashboard, none of that gets captured in code. Here's a few advantages to working this way:įaster Development: Developing locally allows you to work without any network latency or internet disruptions.Įasier Collaboration: Developing locally can make it easier to collaborate with others on the same project.Ĭost-Effective: Supabase provides a generous free plan and gives you two free projects to get started. Given all of the Dashboard's capabilities, you might question the need to work locally. The Dashboard provides a wide range of features for setting up your project: creating tables, adding columns, changing existing columns, creating views, setting up RLS policies, and more. ![]() Working locally, generating migrations as you change your tables, and applying those migrations to a linked project on the Platform keeps everything nicely organized as you grow. ![]() We suggest you work locally and deploy your changes to a linked project on the Supabase Platform.ĭoing things directly on the platform via the Dashboard is fine when you're getting started, but it's a good idea to move to a proper local workflow before you get too far. You can use the Dashboard directly to get up and running quickly, or use a proper local setup. Supabase is a flexible platform that lets you decide how you want to build your projects. ![]()
0 Comments
Leave a Reply. |