Postgres db migration fails on Supabase #83
Unanswered
heavypackets
asked this question in
Help wanted
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm running Shlink via Docker image (stable tag) on Google Cloud Run. Since it's more cost advantageous to use Postgres on Supabase, I've modified the necessary environmental variables to point to the Supabase instance. The initial install to Supabase succeeds (tables are created), but the subsequent migration step does not.
This doesn't appear to be Shlink specific, but I wanted to bring it up anyway. I couldn't find any documentation on this, nor could I determine why Supabase may not support this. Other managed Postgres instances may have the same issue (as this seems to be related to authentication, and they tend to manage authentication in a non-standard way. However, I'm not well-versed enough in the PHP ecosystem to validate this quickly on my own.
Beta Was this translation helpful? Give feedback.
All reactions