Deploying to DigitalOcean and migrating DB with edeliver

Phoenix Forum Questions / Help
, , ,
1

I am getting this error when I try to run:

mix edeliver migrate production --verbose

EDELIVER GUARDIANPRO WITH MIGRATE COMMAND

-----> migrateing production servers

production node:

  user    : deploy
  host    : guard
  path    : /home/deploy/app_release
  response: RPC to 'guardianpro@127.0.0.1' failed: {'EXIT',
                                        {undef,
                                         [{'Guardianpro.Repo',config,[],[]},
                                          {'Elixir.Ecto.Migrator',
                                           verbose_schema_migration,3,
                                           [{file,"lib/ecto/migrator.ex"},
                                            {line,316}]},
                                          {'Elixir.Ecto.Migrator',run,4,
                                           [{file,"lib/ecto/migrator.ex"},
                                            {line,157}]},
                                          {rpc,'-handle_call_call/6-fun-0-',
                                           5,
                                           [{file,"rpc.erl"},{line,197}]}]}}

I have created the DB on the server and ECTO_REPOSITORY=“Guardianpro.Repo” on my .deliver/config file. My DB config in prod.secret.exs on the server is:

# Configure your database

config :guardianpro, Guardianpro.Repo,
adapter: Ecto.Adapters.Postgres,
username: “deploy”,
password: “password”,
database: “guardianpro_prod”,
hostname: “localhost”,
pool_size: 15

To me it looks like it is failing accessing the DB and the guardianpro@127.0.0.1 doesn’t look right… Is it a edeliver config that I am missing?

2

Seems like Guardianpro.Repo.config/0 is undefined. Maybe there’s a typo somewhere?

3

I couldn’t find any typos but ended up removing the

ECTO_REPOSITORY="Guardianpro.Repo" from .deliver/config

I think that combined with adding the hostname: “localhost” to prod.secret.exs on the server did it.?!!