Skip to content

Add documentation for WORDPRESS_DB_HOST #152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 6, 2015
Merged

Add documentation for WORDPRESS_DB_HOST #152

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
92645e9
Add documentation for `WORDPRESS_DB_HOST`
md5 Feb 6, 2015
f85159e
[wordpress] Document need for username/password with external db
md5 Feb 6, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 14 additions & 5 deletions wordpress/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,15 +29,16 @@ Indonesia.
The following environment variables are also honored for configuring your
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_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_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
container, it will be created automatically upon container startup, provided
that the `WORDPRESS_DB_USER` specified has the necessary permissions to create
it.
If the `WORDPRESS_DB_NAME` specified does not already exist on the given MySQL
server, it will be created automatically upon startup of the `wordpress`
container, provided that the `WORDPRESS_DB_USER` specified has the necessary
permissions to create it.

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:
Expand All @@ -47,6 +48,14 @@ container's IP, standard port mappings can be used:
Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a
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` along with the password
in `WORDPRESS_DB_PASSWORD` and the username in `WORDPRESS_DB_USER` (if it is
something other than `root`):

docker run --name some-wordpress -e WORDPRESS_DB_HOST=10.1.2.3:3306 \
-e WORDPRESS_DB_USER=... -e WORDPRESS_DB_PASSWORD=... -d wordpress

# Supported Docker versions

This image is officially supported on Docker version 1.4.1.
Expand Down
19 changes: 14 additions & 5 deletions wordpress/content.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,15 +19,16 @@ Indonesia.
The following environment variables are also honored for configuring your
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_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_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
container, it will be created automatically upon container startup, provided
that the `WORDPRESS_DB_USER` specified has the necessary permissions to create
it.
If the `WORDPRESS_DB_NAME` specified does not already exist on the given MySQL
server, it will be created automatically upon startup of the `wordpress`
container, provided that the `WORDPRESS_DB_USER` specified has the necessary
permissions to create it.

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:
Expand All @@ -36,3 +37,11 @@ container's IP, standard port mappings can be used:

Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a
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` along with the password
in `WORDPRESS_DB_PASSWORD` and the username in `WORDPRESS_DB_USER` (if it is
something other than `root`):

docker run --name some-wordpress -e WORDPRESS_DB_HOST=10.1.2.3:3306 \
-e WORDPRESS_DB_USER=... -e WORDPRESS_DB_PASSWORD=... -d wordpress