Add documentation for `WORDPRESS_DB_HOST`

This commit is contained in:
Mike Dillon 2015-02-05 20:17:32 -08:00
parent 085e98427d
commit 92645e93c8
2 changed files with 22 additions and 10 deletions

View File

@ -29,15 +29,16 @@ Indonesia.
The following environment variables are also honored for configuring your The following environment variables are also honored for configuring your
WordPress instance: WordPress instance:
- `-e WORDPRESS_DB_HOST=...` (defaults to the IP and port of the linked `mysql` container)
- `-e WORDPRESS_DB_USER=...` (defaults to "root") - `-e WORDPRESS_DB_USER=...` (defaults to "root")
- `-e WORDPRESS_DB_PASSWORD=...` (defaults to the value of the `MYSQL_ROOT_PASSWORD` environment variable from the linked mysql container) - `-e WORDPRESS_DB_PASSWORD=...` (defaults to the value of the `MYSQL_ROOT_PASSWORD` environment variable from the linked `mysql` container)
- `-e WORDPRESS_DB_NAME=...` (defaults to "wordpress") - `-e WORDPRESS_DB_NAME=...` (defaults to "wordpress")
- `-e WORDPRESS_AUTH_KEY=...`, `-e WORDPRESS_SECURE_AUTH_KEY=...`, `-e WORDPRESS_LOGGED_IN_KEY=...`, `-e WORDPRESS_NONCE_KEY=...`, `-e WORDPRESS_AUTH_SALT=...`, `-e WORDPRESS_SECURE_AUTH_SALT=...`, `-e WORDPRESS_LOGGED_IN_SALT=...`, `-e WORDPRESS_NONCE_SALT=...` (default to unique random SHA1s) - `-e WORDPRESS_AUTH_KEY=...`, `-e WORDPRESS_SECURE_AUTH_KEY=...`, `-e WORDPRESS_LOGGED_IN_KEY=...`, `-e WORDPRESS_NONCE_KEY=...`, `-e WORDPRESS_AUTH_SALT=...`, `-e WORDPRESS_SECURE_AUTH_SALT=...`, `-e WORDPRESS_LOGGED_IN_SALT=...`, `-e WORDPRESS_NONCE_SALT=...` (default to unique random SHA1s)
If the `WORDPRESS_DB_NAME` specified does not already exist in the given MySQL If the `WORDPRESS_DB_NAME` specified does not already exist on the given MySQL
container, it will be created automatically upon container startup, provided server, it will be created automatically upon startup of the `wordpress`
that the `WORDPRESS_DB_USER` specified has the necessary permissions to create container, provided that the `WORDPRESS_DB_USER` specified has the necessary
it. permissions to create it.
If you'd like to be able to access the instance from the host without the If you'd like to be able to access the instance from the host without the
container's IP, standard port mappings can be used: container's IP, standard port mappings can be used:
@ -47,6 +48,11 @@ container's IP, standard port mappings can be used:
Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a
browser. browser.
If you'd like to use an external database instead of a linked `mysql` container,
specify the hostname and port with `WORDPRESS_DB_HOST`:
docker run --name some-wordpress -e WORDPRESS_DB_HOST=10.1.2.3:3306 -d wordpress
# Supported Docker versions # Supported Docker versions
This image is officially supported on Docker version 1.4.1. This image is officially supported on Docker version 1.4.1.

View File

@ -19,15 +19,16 @@ Indonesia.
The following environment variables are also honored for configuring your The following environment variables are also honored for configuring your
WordPress instance: WordPress instance:
- `-e WORDPRESS_DB_HOST=...` (defaults to the IP and port of the linked `mysql` container)
- `-e WORDPRESS_DB_USER=...` (defaults to "root") - `-e WORDPRESS_DB_USER=...` (defaults to "root")
- `-e WORDPRESS_DB_PASSWORD=...` (defaults to the value of the `MYSQL_ROOT_PASSWORD` environment variable from the linked mysql container) - `-e WORDPRESS_DB_PASSWORD=...` (defaults to the value of the `MYSQL_ROOT_PASSWORD` environment variable from the linked `mysql` container)
- `-e WORDPRESS_DB_NAME=...` (defaults to "wordpress") - `-e WORDPRESS_DB_NAME=...` (defaults to "wordpress")
- `-e WORDPRESS_AUTH_KEY=...`, `-e WORDPRESS_SECURE_AUTH_KEY=...`, `-e WORDPRESS_LOGGED_IN_KEY=...`, `-e WORDPRESS_NONCE_KEY=...`, `-e WORDPRESS_AUTH_SALT=...`, `-e WORDPRESS_SECURE_AUTH_SALT=...`, `-e WORDPRESS_LOGGED_IN_SALT=...`, `-e WORDPRESS_NONCE_SALT=...` (default to unique random SHA1s) - `-e WORDPRESS_AUTH_KEY=...`, `-e WORDPRESS_SECURE_AUTH_KEY=...`, `-e WORDPRESS_LOGGED_IN_KEY=...`, `-e WORDPRESS_NONCE_KEY=...`, `-e WORDPRESS_AUTH_SALT=...`, `-e WORDPRESS_SECURE_AUTH_SALT=...`, `-e WORDPRESS_LOGGED_IN_SALT=...`, `-e WORDPRESS_NONCE_SALT=...` (default to unique random SHA1s)
If the `WORDPRESS_DB_NAME` specified does not already exist in the given MySQL If the `WORDPRESS_DB_NAME` specified does not already exist on the given MySQL
container, it will be created automatically upon container startup, provided server, it will be created automatically upon startup of the `wordpress`
that the `WORDPRESS_DB_USER` specified has the necessary permissions to create container, provided that the `WORDPRESS_DB_USER` specified has the necessary
it. permissions to create it.
If you'd like to be able to access the instance from the host without the If you'd like to be able to access the instance from the host without the
container's IP, standard port mappings can be used: container's IP, standard port mappings can be used:
@ -36,3 +37,8 @@ container's IP, standard port mappings can be used:
Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a
browser. browser.
If you'd like to use an external database instead of a linked `mysql` container,
specify the hostname and port with `WORDPRESS_DB_HOST`:
docker run --name some-wordpress -e WORDPRESS_DB_HOST=10.1.2.3:3306 -d wordpress