Services


MariaDB 10.4 StandAlone

WordPress latest, PHP-FPM 7.3

Redis 5.0

HAProxy latest

Adminer latest

Overview

The stack is suitable for wordpress sites which you can can scale as you want. It provides a one-click install solution for  WordPress + WooCommerce with NGINX caching. The whole deployment takes about 10-15 minutes.

How the WooCommerce stack works

HAProxy on front-end takes requests from users.

WordPress in Docker image based on PHP-FPM + NGINX comes with installed and enabled WP-CLI, WooCommerce, nginx-helper, redis-cache, HyperDB plugins.

As a database is used MariaDB in StandAlone configuration with Redis as object cache

WordPress Light Scalable with NGINX cache

The Scalable WordPress Light with NGINX cache stack design

How to deploy the stack
  1. Click Deploy stack
  2. Sign in or create an account
  3. Choose a provider (how to add a cloud provider) and a region or an existing host (how to add own host to D2C) in Select existing hosts menu
  4. Fill in necessary fields (if they are, e.g. link to your repository)
  5. Click Create hosts and services
Minimal recommended configuration
  • 1 host with 2GB RAM
Configuring custom domain and getting free TLS certificates

You can add your domains with free Let’s Encrypt certificates using the following instruction:

  • Open a HAProxy service 
  • click “Edit settings”
  • find “Configure services” block
  • choose Own domains and specify domains and/or subdomains at domains field
  • click Update service
Working with Git

You can keep themes and plugins in your Git repositories. If you use this option, don’t forget to remove /themes and /plugins volumes in “Persistent data volumes” block.

Checking logs of containers (php, nginx, etc.)

You can check live logs at the page of a container. Please, follow the instructions from the Help Center. You may also find information about D2C logs in the documentation.

Changes in your config files

You can find and edit your configs using the following instruction:

  • open a PHP-FPM service (name “blog” by default in the stack)
  • click “Edit settings
  • find “Configs” block
After deploying

You can: