Running Wordpress in a Docker Container - Appcontainers/wordpress review

In this video, I run through a wordpress docker container setup, including all of the components required to fully customize the container, as well as demonstrate how to run it in standalone vs production mode.

[Formatccolonvideo]

Updated the wordpress container build tonight. There is now an option for MODE which has 3 settings.

1. -e MODE=’standalone’ – Works as it did before, allowing a single setup all on one box

2. -e MODE=’new’ – This will use the other variables to establish a connection to a remote mysql server, and using the MYSQL_USER, MYSQL_PASS, MYSQL_SERVER, MYSQL_CLIENT, MYSQL_DB, APP_USER, APP_PASS variables, it will create a new database on the remote server and set the grants. The caveat being that you must already have a user with grant options setup on the mysql server that has access to all databases. On the local wordpress container, if new is selected, then the MySQL instance is never initialized, or started. This basically puts the server back into the traditional docker paradigm of single service in a container.

3. -e MODE=’existing’ – This will also use the other variables to establish a connection to a remote mysql server, and using the MYSQL_SERVER, MYSQL_DB, APP_USER, APP_PASS variables to simply initialize a connection to an existing wordpress database on an existing remote database server. It assumes that the database is there, has all of its tables from a previous installation, and does not alter the database server at all. Its simply a connect only setting. Again, this the MySQL instance is never initialized, or started. It assumes that the credentials that are supplied for APP_USER, and APP_PASS are already existing grants on the remote mysql server.