Merge pull request #106 from infosiftr/added_caveats
Add a notice for behavior on database initialization
This commit is contained in:
commit
658752dd73
|
|
@ -75,6 +75,14 @@ a user/password was supplied (via the `MYSQL_USER` and `MYSQL_PASSWORD`
|
|||
environment variables) then that user account will be granted (`GRANT ALL`)
|
||||
access to this database.
|
||||
|
||||
# Caveats
|
||||
|
||||
If there is no database when `mysql` starts in a container, then `mysql` will
|
||||
create the default database for you. While this is the expected behavior of
|
||||
`mysql`, this means that it will not accept incoming connections during that
|
||||
time. This may cause issues when using automation tools, such as `fig`, that
|
||||
start several containers simultaneously.
|
||||
|
||||
# User Feedback
|
||||
|
||||
## Issues
|
||||
|
|
|
|||
|
|
@ -62,3 +62,11 @@ This optional environment variable denotes the name of a database to create. If
|
|||
a user/password was supplied (via the `MYSQL_USER` and `MYSQL_PASSWORD`
|
||||
environment variables) then that user account will be granted (`GRANT ALL`)
|
||||
access to this database.
|
||||
|
||||
# Caveats
|
||||
|
||||
If there is no database when `mysql` starts in a container, then `mysql` will
|
||||
create the default database for you. While this is the expected behavior of
|
||||
`mysql`, this means that it will not accept incoming connections during that
|
||||
time. This may cause issues when using automation tools, such as `fig`, that
|
||||
start several containers simultaneously.
|
||||
|
|
|
|||
|
|
@ -77,6 +77,14 @@ Postgres'' [single user
|
|||
mode](http://www.postgresql.org/docs/9.3/static/app-postgres.html#AEN90580) is
|
||||
highly recommended.
|
||||
|
||||
# Caveats
|
||||
|
||||
If there is no database when `postgres` starts in a container, then `postgres` will
|
||||
create the default database for you. While this is the expected behavior of
|
||||
`postgres`, this means that it will not accept incoming connections during that
|
||||
time. This may cause issues when using automation tools, such as `fig`, that
|
||||
start several containers simultaneously.
|
||||
|
||||
# User Feedback
|
||||
|
||||
## Issues
|
||||
|
|
|
|||
|
|
@ -61,3 +61,11 @@ need to execute SQL commands as part of your initialization, the use of
|
|||
Postgres'' [single user
|
||||
mode](http://www.postgresql.org/docs/9.3/static/app-postgres.html#AEN90580) is
|
||||
highly recommended.
|
||||
|
||||
# Caveats
|
||||
|
||||
If there is no database when `postgres` starts in a container, then `postgres` will
|
||||
create the default database for you. While this is the expected behavior of
|
||||
`postgres`, this means that it will not accept incoming connections during that
|
||||
time. This may cause issues when using automation tools, such as `fig`, that
|
||||
start several containers simultaneously.
|
||||
|
|
|
|||
Loading…
Reference in New Issue