https://github.com/bit4bit/ecto_sql_readiness
Is Ecto ready to handle connections?
https://github.com/bit4bit/ecto_sql_readiness
Last synced: 9 months ago
JSON representation
Is Ecto ready to handle connections?
- Host: GitHub
- URL: https://github.com/bit4bit/ecto_sql_readiness
- Owner: bit4bit
- License: apache-2.0
- Created: 2023-11-20T13:49:21.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2025-04-12T20:38:44.000Z (about 1 year ago)
- Last Synced: 2025-10-21T15:49:28.214Z (9 months ago)
- Language: Elixir
- Size: 10.7 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# 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](https://hex.pm/docs/publish), the package can be installed
by adding `ecto_sql_readiness` to your list of dependencies in `mix.exs`:
```elixir
def deps do
[
{:ecto_sql_readiness, "~> 0.2"}
]
end
```
Documentation can be generated with [ExDoc](https://github.com/elixir-lang/ex_doc)
and published on [HexDocs](https://hexdocs.pm). Once published, the docs can
be found at .
## Contributing
1. `code`
2. `MIX_ENV=test mix check`