Muliira Ham Ibrahim

If you haven't done it already i recommend posting this in the #jobs channel inside of discord as there tends to be a bit more activity there

These are a bit old so not sure how helpful they would still be https://supabase.com/blog/using-supabase-replit and https://blog.replit.com/making-real-time-chat-app-with-supabase-on-replit

Any chance you are affected by the current issues with ISPs in india https://status.supabase.com/

I had a look on my side and it found the same issue. Perhaps this is a bug, in which case you can add it as an issue in the cli repo https://github.com/supabase/cli/issues

I'm not sure what claude is referring to here but the defaut for Supabase is IPV6 https://supabase.com/docs/guides/platform/ipv4-address. I'm not sure if Railway is one of the ones that needs IPV4 but if you head to the connection tab in the dashboard home page you can use different connection strings for your Database including the session pooler for IPv4 <img width="313" height="40" alt="image" src="https://github.com/user-attachments/assets/aca67739-9fc2-4b3d-a976-61807cf8a8ea" />

Would cloning the Supabase Github repo locally help?

What is your setup currently. If you are using the main branch to deploy to staging and prod, then if you have Supabase connected to Github wouldn't you update your prod database whenever you push a change to the main branch before you even get to the staging deployment? I'm wondering if the issue is less branching but the fact that any pushes to main is not necessarily a push to your prod database?

Might recommend adding thoughts to this branching discussion here https://github.com/orgs/supabase/discussions/18937

looks cool, there is a showcase channel on discord also if you want to share it there

For what it is worth this feature does already exist i think but only for team/enterprise https://supabase.com/docs/guides/platform/access-control

It is saying that `site_content` could not be found. I assume you just need to create the table and it's columns.

Reach out to support i reckon is the best plan of action, they'll have more visibility into internal changes like that

Unpausing a project wouldn't cause any errors. What was the reason it was paused? Not used for 7 days or did you pause it?