bit4bit/ecto_sql_readiness

Is Ecto ready to handle connections?

EctoSqlReadiness

How can we ensure that there are no pending migration during deployment? How can we ensure that Ecto is ready?

This library has been used with AWS Codedeploy, so we don't send any traffic to the containers unless we ensure that Ecto is ready to work.

Installation

If available in Hex, the package can be installed by adding ecto_sql_readiness to your list of dependencies in mix.exs:

def deps do
  [
    {:ecto_sql_readiness, "~> 0.2"}
  ]
end

Documentation can be generated with ExDoc and published on HexDocs. Once published, the docs can be found at https://hexdocs.pm/ecto_sql_readiness.

Contributing

1. code
2. MIX_ENV=test mix check