Listing the complete solution, to the blocker and to remaining issues I had to resolve to restore full migrate and deploy capability:
- to unblock and get expected output during deploy, ran
fly scale count 1
one time (since was at 0), before running deploy command above - uncommented the line in
Dockerfile
forENV ERL_AFLAGS "-proto_dist inet6_tcp"
since it seemed needed for Fly.io network (even though the database is outside that network) - set
DATABASE_URL
to the CrunchyBridge DB’s v6 IP address and then needed to changeECTO_IPV6
totrue
in theDockerfile
- added to config options in
runtime.exs
aboveafter_connect: {EctoConnectionCheck, :log_connection_success, [Myapp.Repo]}
, in order to confirm connection succeeded (to eliminate possible issues under consideration) - granted / altered some database permissions (not necessary, in general, if already set up correctly)
- added back the deploy
release_command
above to thefly.toml
that calls the app-specific Procfile above via overmind - in
Myapp.Release
, attempted to add:debug
in options toEcto.Migrator.run/3
but they were ineffective:log_level
,log_migrations_sql
,log_migrator_sql
(will re-test and file bug report onecto_sql
as necessary