WordPress Docker Project

🚛 Truck Signs API

This page documents how I configured my very first cloud server instance in the Developer Akademie DevSecOps Course.

TOC

Github Tip

URL: https://github.com/Gosia2024/wordpress

WordPress Docker Project

Table of Contents

• WordPress Docker Project
• 🚛 Truck Signs API
  • TOC
• WordPress Docker Project
  • Table of Contents
  • Description
  • Quickstart
    • Prerequisites
    • Run
    • Usage
    • Configuration
      • Docker Compose details
    • Restarting the setup
    • Creating the .env File
    • Logging into WordPress and Adding a Test Post
  • Security Notes
  • Testing

Description

This repository contains a Docker Compose setup to deploy a WordPress site with a MySQL database.
The setup uses official Docker images, persists data with Docker volumes, and configures environment variables for flexibility.
The purpose is to provide a ready-to-run WordPress environment suitable for deployment on a cloud VM.

Quickstart

Prerequisites

• Docker installed (docs.docker.com/get-docker)
• Docker Compose installed (docs.docker.com/compose/install)
• Access to a machine or VM where you want to deploy

Run

1. Clone this repository and navigate into the project folder:

git clone https://github.com/Gosia2024/wordpress.git
cd wordpress

1. Create a .env file in the project root (see Creating the .env File).
2. Start the containers:

docker-compose up -d

Open your browser and go to http://localhost:8080 (or http://YOUR_VM_IP:8080 on your cloud VM).

Usage

Configuration

Environment variables are set in the .env file:

• WORDPRESS_DB_USER — MySQL user for WordPress
• WORDPRESS_DB_PASSWORD — Password for MySQL user
• WORDPRESS_DB_NAME — Database name
• MYSQL_ROOT_PASSWORD — Root password for MySQL

You can modify these values in your .env file before starting the containers.

Docker Compose details

Two services are defined:

• wordpress — runs the WordPress application
• db — runs the MySQL database
  Both services run on the default Docker network created by Compose to allow communication.
  Both services use restart: on-failure to automatically restart if they exit unexpectedly.

Volumes (wordpress_data, db_data) persist data between container restarts.

Restarting the setup

To stop the services:

docker-compose down

Your WordPress data and database will persist across restarts due to volume usage.

Creating the .env File

On your local machine or server, create the .env file in the root directory of the project.

Paste the following environment variables into the file:

WORDPRESS_DB_USER=wordpressuser
WORDPRESS_DB_PASSWORD=securepassword
WORDPRESS_DB_NAME=wordpressdb
MYSQL_ROOT_PASSWORD=rootpassword

Save the file with Ctrl + O, press Enter, and exit with Ctrl + X.

Logging into WordPress and Adding a Test Post

After you complete the WordPress installation and log in:

1. Navigate to the WordPress admin dashboard.

2. Go to Posts → Add New.

3. Create a test post, for example, titled "Hello World".

4. Publish the post.

5. Verify that the post appears on the homepage of your WordPress site.

This confirms that your WordPress installation is working properly and data persistence is functioning as expected.

Security Notes

• Do not store passwords, tokens, or sensitive information directly in the repository.
• Use environment variables defined in the .env file for all sensitive data.
• The .env file is included in .gitignore to prevent accidental commits.
• Use ${VARIABLE_NAME} syntax in docker-compose.yaml to reference environment variables.
• Follow naming conventions: environment variables should be uppercase with underscores.

Testing

Before submitting the project, ensure:

• WordPress is accessible at the IP address of your cloud VM on port 8080.
• You can log in with the configured admin user credentials.
• Data remains intact after restarting the containers.
• Containers automatically restart if they exit unexpectedly.