WooCommerce is a free e-commerce plugin used as an extension for WordPress. It provides powerful tools for creating online stores, including product management, order processing, payment and shipping management, and more. WooCommerce is one of the most widely used e-commerce solutions in the world, known for its flexibility and easy integration with various platforms and payment gateways.
In this image, WordPress is installed together with WooCommerce to reduce deployment time.
| Package | Version |
|---|---|
| Wordpress + Woocommerce | latest |
| Docker | 3.20.10 |
| Docker compose | 2.12.2 |
| containerd.io | 1.6.10 |
This application uses Docker to provide faster startup of the accompanying software (WordPress + Woocommerce) and direct use. This eliminates the need to familiarize yourself with its specifics in terms of configuration and installation. To start working directly with the application, all you need to do is visit the IP address assigned to your virtual machine in your browser to view your new WooCommerce installation.
Note: By default, Wordpress + Woocommerce can be accessed directly by IP address. To start using Wordpress + Woocommerce with your real domain, you must first point the domain in question to your IP address and change the settings for where Wordpress + Woocommerce opens from its admin panel.
docker and docker compose commands are now available in this application./opt/wordpress/data/. MariaDB is also persistent and stores its databases in /opt/mariadb/data/.admin and the password is P@ssw0rd!.WordPress Address (URL) and Site Address (URL) in the Wordpress administrative panel are grayed out and are inactive. These options are set in the wp-config.php file and are overriding the settings in in web panel. If you want to edit the settings directly via the web panel, then you will need to open your wp-config.php file and remove or comment out the rows 'WP_HOME', 'http://' . $_SERVER['HTTP_HOST'] . '/' ); and define( 'WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST'] . '/' );.if ( !defined( 'WP_CLI' ) ) {
// remove x-pingback HTTP header
add_filter("wp_headers", function($headers) {
unset($headers["X-Pingback"]);
return $headers;
});
// disable pingbacks
add_filter( "xmlrpc_methods", function( $methods ) {
unset( $methods["pingback.ping"] );
return $methods;
});
}
Additional settings for Wordpress + Woocommerce that you can change and that are controlled directly by Docker are set as variables in the configuration file /opt/docker-wordpress/docker-compose.yml:
Note: After changing any of the values, you must recreate the Docker container on which the application is running. For more information, please read the Recreating Docker containers section.
If you already have ready-made, valid certificates, you need to make a few configuration modifications before you can use them. To achieve this, please follow these steps:
Create a directory where the certificates will be stored:
mkdir /opt/certs/
Copy the certificates into the directory you just created and modify their permissions:
chown 1001:1001 /opt/certs/ -R
Open the docker configuration file /opt/docker-wordpress/docker-compose.yml with a text editor and find the following snippet:
wordpress:
image: docker.io/bitnami/wordpress:6
ports:
- '80:8080'
- '443:8443'
volumes:
- '/opt/wordpress/data:/bitnami/wordpress'
Edit it so it looks like this:
wordpress:
image: docker.io/bitnami/wordpress:6
ports:
- '80:8080'
- '443:8443'
volumes:
- '/opt/wordpress/data:/bitnami/wordpress'
- '/opt/certs/cert.pem:/opt/bitnami/apache/conf/bitnami/certs/server.crt'
- '/opt/certs/privkey.pem:/opt/bitnami/apache/conf/bitnami/certs/server.key'
Note that /opt/certs/cert.pem is the path to the certificate and /opt/certs/privkey.pem is the path to the private key. You can name the files and directories as you wish, but they must be specified correctly in the configuration
cd /opt/docker-wordpress/
docker compose up -d
If you wish, you can always issue free certificates from Letsencrypt as well. To do this, please follow the steps below:
Login to your server as root and run the following commands:
dnf install -y epel-release
dnf install -y certbot
Please note that in order for a free certificate to be issued, you must be able to verify your domain ownership in some way. Letsencrypt provides several options for verifying your domains, in this example we will use verification by running a temporary web server.
To do this, temporarily stop the container with the docker stop docker-wordpress-wordpress-1 command. Important: Performing this step will temporarily stop your site from working. Make sure you perform this action at a time when it will least affect your users.
Issue the certificate with the command certbot certonly --standalone --preferred-challenges http -d example.com, replacing "example.com" with the domain you pointed to your Cloud server IP address.
Open the docker configuration file /opt/docker-wordpress/docker-compose.yml with a text editor and find the following snippet:
wordpress:
image: docker.io/bitnami/wordpress:6
ports:
- '80:8080'
- '443:8443'
volumes:
- '/opt/wordpress/data/:/bitnami/wordpress'
Edit it so it looks like this:
wordpress:
image: docker.io/bitnami/wordpress:6
ports:
- '80:8080'
- '443:8443'
volumes:
- '/opt/wordpress/data/:/bitnami/wordpress'
- '/etc/letsencrypt/live/example.com/cert.pem:/opt/bitnami/apache/conf/bitnami/certs/server.crt'
- '/etc/letsencrypt/live/example.com/privkey.pem:/opt/bitnami/apache/conf/bitnami/certs/server.key'
With this modification, you end up "binding" the external certificates issued by Letsencrypt to the configuration that resides inside the docker container. Replace "example.com" with your domain name. After you change the configuration, you need to fix the certificate permissions with the command chown 1001:1001 /etc/letsencrypt/archive/example.com/ -R, again replacing "example.com" with your domain name.
Since the docker container is temporarily stopped, it needs to apply the new configuration and start it. Please run the following commands:
cd /opt/docker-wordpress/
docker compose up -d
Automatic renewal can be arranged via cron. You can set the following cron configuration to make auto-renewal happen:
# Automated Letsencrypt renewal
0 0 * * * /usr/bin/certbot renew --pre-hook 'docker stop docker-wordpress-wordpress-1' --post-hook 'chown 1001:1001 /etc/letsencrypt/archive/example.com/ -R; docker start docker-wordpress-wordpress-1'
Of course, you can change the runtime whenever you want. In the above example, this task will run every day at 00:00.
The organization of this application is entirely done using Docker. In this way, we can provide you with ready-made applications faster. In addition, their configuration is more flexible and quite controllable. To be able to control this application, however, you need to know some basic Docker functionalities and features.
Restarting the database and the Docker container that contains Wordpress itself, along with the rest of the software, can be done in two ways:
sudo su -
cd /opt/docker-wordpress/
docker compose restart
Recreation of a docker container may be necessary if you've changed the configuration inside the docker-compose.yml file. If there are changes, please follow these steps:
cd /opt/docker-wordpress/
docker compose stop
docker compose up -d
To check, you need to run the following commands:
sudo su -
docker ps -a
Please pay attention to the STATUS column. It should show how long the service has been running, for example Up X minutes. If the status is Restarting then you need to check what is wrong with the application. In such a case, you can check by following the application logs as follows:
NAMES column from the output of the docker ps -a command. View the logs with the docker logs <NAME> command, where The settings in section Additional Docker settings can be set in the docker-compose.yml file. The path to it is described again in this section. To change a setting, open the configuration file and note the environment section under wordpress. Each configuration option must be described on a new line with a dash in front, as in the following example:
environment:
- ALLOW_EMPTY_PASSWORD=yes
- WORDPRESS_DATABASE_HOST=mariadb
- WORDPRESS_DATABASE_PORT_NUMBER=3306
- WORDPRESS_DATABASE_USER=wordpress
- WORDPRESS_DATABASE_NAME=wordpress
- WORDPRESS_USERNAME=admin
- WORDPRESS_PASSWORD=P@ssw0rd!
- WORDPRESS_EMAIL=admin@example.com
- WORDPRESS_PLUGINS=woocommerce
Please note that the correct indentation (number of spaces) must also be observed, as this is important for yaml configuration files.