However, I was struggling with getting started, because the WordPress container is just… WordPress. It also needs a database to work, and my Docker experience was not yet strong enough to sort out how to link various containers together. So I raised an issue on Github asking about a step-by-step tutorial.
Github user wglambert very kindly provided a simple docker-compose.yaml file that could launch both WordPress and MySQL in separate containers and set up the necessary network and links.
It works wonderfully! And it has now been added to the instructions on DockerHub. (Thank you to the DockerHub admins for merging it in.)
Because I want to easily use the file on different systems, I put it up in a Github repo:
As I noted in my Disruptive Conversations article, I’m planning to start writing here a good bit more about using Docker. I’m rather impressed by all that can be done – and want to capture my own experiments here for my own future knowledge… and if it helps any of you all out, too, all the better!
In addition to being where I write about programming and other developer topics, this site is also where I test out new WordPress releases before installing them on other sites like the Voxeo blog portal or the Voice of VOIPSA site. This site runs on a WordPress Multi-Site installation, although there aren’t many sites here (another one is my new IPv6 book).
This past week I installed WordPress 3.2 (followed by the 3.2.1 bug fix) and I have to say I am quite impressed with the back-end changes described in the announcement. Some of them are just minor little nuances… the changes in the typography, even… it just feels snappier and faster. If you run a blog on top of WordPress, I have to say that 3.2 is definitely worth a look… I’m loving it!