From 2eda885281e04877b6d6c1aa2756a5e45972efeb Mon Sep 17 00:00:00 2001 From: Tianon Gravi Date: Tue, 28 Apr 2015 16:49:06 -0600 Subject: [PATCH] Update wordpress to use %%REPO%% more aggressively so sections can be reused without change more often --- wordpress/content.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/wordpress/content.md b/wordpress/content.md index 90e453010..fcdbf7e18 100644 --- a/wordpress/content.md +++ b/wordpress/content.md @@ -8,7 +8,7 @@ WordPress is a free and open source blogging tool and a content management syste # How to use this image - docker run --name some-wordpress --link some-mysql:mysql -d wordpress + docker run --name some-%%REPO%% --link some-mysql:mysql -d %%REPO%% The following environment variables are also honored for configuring your WordPress instance: @@ -18,18 +18,18 @@ The following environment variables are also honored for configuring your WordPr - `-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 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 the `WORDPRESS_DB_NAME` specified does not already exist on the given MySQL server, it will be created automatically upon startup of the `%%REPO%%` 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: - docker run --name some-wordpress --link some-mysql:mysql -p 8080:80 -d wordpress + docker run --name some-%%REPO%% --link some-mysql:mysql -p 8080:80 -d %%REPO%% 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 + docker run --name some-%%REPO%% -e WORDPRESS_DB_HOST=10.1.2.3:3306 \ + -e WORDPRESS_DB_USER=... -e WORDPRESS_DB_PASSWORD=... -d %%REPO%% ## %%COMPOSE%% @@ -44,4 +44,4 @@ If you need additional PHP extensions, you'll need to create your own image `FRO The following Docker Hub features can help with the task of keeping your dependent images up-to-date: - [Automated Builds](https://docs.docker.com/docker-hub/builds/) let Docker Hub automatically build your Dockerfile each time you push changes to it. -- [Repository Links](https://docs.docker.com/docker-hub/builds/#repository-links) can ensure that your image is also rebuilt any time `wordpress` is updated. +- [Repository Links](https://docs.docker.com/docker-hub/builds/#repository-links) can ensure that your image is also rebuilt any time `%%REPO%%` is updated.