Supabase Managed Postgres in private alpha

[pier]

Supabase is GA now and from their blog post they will do a Fly announcement this week

[joshua-fly]

Folks, Supabase on Fly.io is now in public beta. Here’s the post!

Supabase Postgres available to everyone in public beta

Supabase Postgres on Fly.io is now in public beta! Bring over your toughest test workloads. Anyone with a Fly account can provision a database in any Fly.io region with: fly ext supabase create Here’s the annoucement from Supabase and our docs for getting started. Here’s a perk: You can now test Supabase Branching, an opt-in feature which creates an ephemeral test environment for your git branches. These instances automatically pause when you aren’t using them to save on costs. Learn more a…

[barbinbrad]

When I spin up a database in Fly I get a DATABASE_URL and DATABASE_POOLER_URL. How can I get a service role key, database password, and project ID given that information? I’m hoping to do this all through scripting.

[julianrubisch]

Sorry to reiterate on this, but has there been any movement here? Any tutorial or blog post?

I envision something more reliable than just doing a pg_dump and pg_restore. Maybe setting up a logical replication, then switch.

[bradford1]

@yharaskrik

Hey Joshua, does that include private DBs? (Ie. Within our wire guard network so they are not accessible publicly?)

Actually, this makes me believe that securely using Supabase as public db with Fly.io might not be feasible at all. Since Fly.io doesn’t offer static outbound IPs, configuring network restrictions becomes impossible (unless you another 3rd party https://usefixie.com)

[joshua-fly]

@julianrubisch

Sorry to reiterate on this, but has there been any movement here? Any tutorial or blog post?

I envision something more reliable than just doing a pg_dump and pg_restore. Maybe setting up a logical replication, then switch.

There’s no official tooling for migration, yet. However, setting up logical replication is pretty straightforward, as you can see in this recently minted guide.

We’d love to write something up, or even work on tooling to automate a migration, but we’re now focused on reliability. Once we get to beta, we can revisit this topic.

[julianrubisch]

Thank you!

I looked into logical replication, of course, but it seems it’s not supported from the Supabase side: Roles, superuser access and unsupported operations | Supabase Docs

or is there some special setup/environment for Fly customers?

[joshua-fly]

@julianrubisch

Thank you!

I looked into logical replication, of course, but it seems it’s not supported from the Supabase side: Roles, superuser access and unsupported operations | Supabase Docs

or is there some special setup/environment for Fly customers?

Yes, you’re right, I had forgotten about this change. There’s no special setup, but we’re discussing the possibility of opening it up for the db initialization phase.

[mayailurus]

@bradford1

Since Fly.io doesn’t offer static outbound IPs

These are on the horizon, actually… They were mentioned recently in the (excellent but much overlooked) Infrastructure Log:

Steve has had a fun week. He’s working on shipping (you heard it here first) static IP address assignments for individual Fly Machines — this means Fly Machines can make direct requests to the Internet (for instance, to internal on-prem APIs) with predictable IP addresses.

And subsequently…

Steve finished up the provisioning tooling for the fou-tunnel-and-SNAT monstrosity that we talked about last week: giving Fly Machines static IP addresses, for people who talk to IP-restricted 3rd party APIs.

Whether or not it helps with security, , it definitely will improve compatibility.

[charsleysa]

@mayailurus

They were mentioned recently in the (excellent but much overlooked) Infrastructure Log:

Would be awesome if these were cross posted to the forum so we can be notified.

[yharaskrik]

Oh this is great news! Would still be nice if we could run it from within our fly network obviously so it’s not even open to the Internet but I’ll take static IPs