Sorry @outlog just checking this is what you meant:
My new test config file:
# Configure your database
config :ev2, Ev2.Repo,
adapter: Ecto.Adapters.Postgres,
url: System.get_env("DATABASE_URL"),
pool: Ecto.Adapters.SQL.Sandbox
Which yielded the same setup error:
13:21:49.770 [error] Postgrex.Protocol (#PID<0.1220.0>) failed to connect: ** (Postgrex.Error) ssl not available
13:21:49.775 [error] Could not retrieve migrated versions. This error usually happens due to the following:
* The database does not exist
* The "schema_migrations" table, which Ecto uses for managing
migrations, was defined by another library
To fix the first issue, run "mix ecto.create".
To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create". Alternatively you may configure Ecto to use
another table for managing migrations:
config :ev2, Ev2.Repo,
migration_source: "some_other_table_for_schema_migrations"
The full error report is shown below.
** (DBConnection.ConnectionError) connection not available because of disconnection
And by this:
only thing that pops out is that DB config - that really shouldn’t work against localhost…
Did you mean my original config? shouldn’t work against localhost on my machine or against localhost against the Heroku test db?
