Will the new release of flyctl
v0.0.470
fix and apply this automatically from now on
Yeah, should address it automatically.
Will the new release of flyctl
v0.0.470
fix and apply this automatically from now on
Yeah, should address it automatically.
Thank you @shaun the updated script worked like a charm.
FYI just running fly deploy
again gave the same error as before, I guess this is expected.
What worked was to delete fly.toml
and Dockerfile
from the app directory, and then run fly launch
again.
This time the postgres migration incl CREATE EXTENSION IF NOT EXISTS citext
succeeded and the deployment reached its conclusion.
Much appreciate you providing the update @shaun!
FWIW, I am on fly v0.0.470 and just ran into this issue
for anyone after me, I followed the advice in the previous post, namely adding SUPERUSER
privileges. you can get the user name by running fly ssh console
, then env
to see the DATABASE_URL
. The database url has the following format: postgres://<username>:<password>@<host>/<db_name>
, so just find the section right after postgres://
, up to the colon.
Then fly pg connect -a my-app-db
to run the ALTER user
command in @shaun 's post.
For some reason I am not able to ssh into my app, I am getting following error:
Error no instances found for <app_name>
I can see my instance in the web console and its in pending state.