I have a somewhat unusual use case: A publicly available Postgres server with PostGIS for (infrequent) use with QGis.
I understand why Fly doesn't want customers to expose the database to the rest of the internet (ecosystem and such), but am very happy that Railway allows it.
I understand why Fly doesn't want customers to expose the database to the rest of the internet (ecosystem and such), but am very happy that Railway allows it.