I haven’t updated this site in a long time, but I’ve been paying a monthly hosting fee all along. This year, when the site came up for renewal with Bluehost, I felt their prices where high, and their pricing scheme was deceptive. I wasn’t able to switch packages to the lower tier on the dashboard, and when I called in the price quoted wasn’t the same price on the website. Before calling, I decided I’d not let the call run for more than 5 minutes, if they couldn’t figure it out that fast, I might as well self-host; I’ve been wanted to set this up a while anyway.
First, Get a Server
You’re going to need a server, I am going to assume you know how to get a server up and running. I used a nano AWS instance, but a basic Digital Ocean droplet would do nicely.
Prepare the Server
Now you’re going to need to do is install Docker, and Docker Compose. SSH in to the server and let’s get started. The lines below are meant for Amazon Linux, if you’re using something else, you will need to adjust accordingly:
# Update your packages, always good to start with this. sudo yum update -y # Install Docker sudo yum install docker # Start Docker sudo service docker start # Allow the default ec2-user to interact with Docker sudo setfacl --modify user:ec2-user:rw /var/run/docker.sock # Install Docker-Compose (all one line, wrapped because of WordPress) sudo curl -L https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m) -o /usr/local/bin/docker-compose # Enable Docker-Compose to be executable sudo chmod +x /usr/local/bin/docker-compose # Make sure Docker-Compose is working docker-compose version # If you see "Docker Compose version v2.1.1", it worked!
Now you’ve got your machine all ready to go, let’s install the software
Optional Swap Space
If you’ve chosen a server that doesn’t have much memory, like me, you will probably see errors when you start the Docker network, I’ve added 2GB of swap space to fix this:
# Create a 2GB file sudo fallocate -l 2G swap # Set the file permissions sudo chmod 600 swap # Turn it in to a swap sudo mkswap swap # Enable the swap sudo swapon swap
Install WordPress + MySQL + Redis
Let’s install all the software.
# Create the directory for the files, chown it, and enter it sudo mkdir /var/WordPress sudo chown ec2-user:ec2-user /var/WordPress cd /var/WordPress # Open "docker-compose.yml" to editing nano docker-compose.yml
The last line above should open a basic text editor called Nano. Copy and past the following contents in to the file, I will break down this file below. After pasting use “ctrl+x” , “y”, “enter” to save it.
version: "3.9" services: wordpress: image: "wordpress:latest" restart: always ports: - 80:80 environment: WORDPRESS_DB_HOST: db WORDPRESS_DB_USER: wp_user WORDPRESS_DB_PASSWORD: secret_password WORDPRESS_DB_NAME: wp_database volumes: - ./site:/var/www/html db: image: "mysql:5.7" restart: always environment: MYSQL_DATABASE: wp_database MYSQL_USER: wp_user MYSQL_PASSWORD: secret_password MYSQL_RANDOM_ROOT_PASSWORD: '1' volumes: - ./data:/var/lib/mysql redis: image: "redis:alpine"
Version 3.9 is the version of the docker-compose, nothing special here. This creates a network of 3 containers; a WordPress container that maps port 80 of the host to the container. A “db” container, which consists of MySql 5.7, you might have noticed there is a random root password, you will not need to access the database as root, so we can do this. Lastly, a generic Redis container.
It’s not good practice to embed your secret password in the open like I did above. You should use Docker secrets for this, but for now, this will do.
Turn it on!
Use the following command to turn it on:
You should see a lot of text on the screen, once it’s up and running, test it by visiting http://<SERVER IP> in your browser. You should see this:
If this works, go back to your SSH session and hit ctrl+c to stop the network. Let’s run it in detached mode (so it stays running in the background):
docker-compose up -d
Now go back to your browser and go ahead and setup your WordPress instance, we still need to finish off setting up Redis. Continue once you’ve setup WordPress.
Enabling Redis for Max Performance
Go to “Plugins” and top the “Add New” button.
Search for “redis” and install “Redis Object Cache”
Don’t forget to activate it!
Now go to settings:
and enabled it:
We’re not yet done, this will result in a “Status: Not connected”. This is expected because by default this plugin tries to connect to localhost as the Redis server, we need to change it. Let’s go back to our SSH session.
# Edit to the wp-config.php file sudo nano /var/WordPress/site/wp-config.php # Add this after "<?php" to use "redis" as the hostname. define('WP_REDIS_HOST', 'redis'); # ctrl+x , y , enter to save
Finally, refresh the WordPress admin panel and you should have WordPress connected to Redis
That’s all! You can not setup your WordPress instance and can use it as you wish!