# Supabase Test vs Live Database (if possible)

**URL:** <https://community.weweb.io/t/supabase-test-vs-live-database-if-possible/4758>\
**Category:** How do I?\
**Tags:** supabase\
**Created:** [October 5, 2023, 8:56pm UTC](https://community.weweb.io/t/supabase-test-vs-live-database-if-possible/4758 "2023-10-05T20:56:04Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![kanepaamauloa](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kanepaamauloa/32/8944_2.png) [@kanepaamauloa](https://community.weweb.io/u/kanepaamauloa)\
**Post date:** [June 7, 2024, 3:07am UTC](https://community.weweb.io/t/supabase-test-vs-live-database-if-possible/4758/21 "2024-06-07T03:07:40Z")

</div>

What browser is @flo using?! 🙂

### UPDATE

Found it! [https://arc.net/](https://arc.net/)

ALSO, thanks for this video! Great to know we can use a local supabase instance. I was just in the process of setting up a local supabase because of the migration feature, but I was wondering how I would continue developing. I thought I’d have to keep doing a `supabase db pull` everytime I changed the db on the platform to keep writing migrations.

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [June 7, 2024, 6:02am UTC](https://community.weweb.io/t/supabase-test-vs-live-database-if-possible/4758/22 "2024-06-07T06:02:45Z")

</div>

Yes, that’s exactly what you do. You no longer edit the production via the Editor / SQL, but you instead do everything on local and push the changes to production via migrations

[Previous page](https://community.weweb.io/t/supabase-test-vs-live-database-if-possible/4758.md?page=1)
