Public | Automated Build

Last pushed: 2 years ago
Short Description
EasyEngine image with stack services. Instantly configurable to Redis/TotalCache, HHVM, etc
Full Description


Orchestrate/Pre-Build the 15mins EasyEngine WordPress deployment into Docker image.

Once completed, we will be going to have:

1- Vanilla Official Ubuntu:14.04 docker base image

2- EasyEngine base installation created:

apt-get install wget
wget -qO ee && sudo bash ee
source /etc/bash_completion.d/ee_auto.rc

3- Next step is to run that base image and going inside setup the required stack and starting the services: MySQL (MariaDB), Web (Nginx + php5-fpm) and some admin utils

ee stack install
ee stack start

4- Once completed, a popular WordPress site is ready to get built automatically by the following command:

ee site create --user=YOURUSER --pass=YOURPSW --email=YOUREMAIL
  • Or if you like to start with multi-site wordpress:
    ee site create --user=YOURUSER --pass=YOURPSW --email=YOUREMAIL --wpsubdom

Alternative to step (3), we could create a pre-build stack image as follows:

docker build -t ee-stack -f ee-stack/Dockerfile .

And then run ee-stack:

docker run --rm -p 80:80 -p 443:443 -p 22222:22222 ee-stack

A file type mis-match warning could be ignored if encountered. Note that 'ee stack start' will be triggered automatically.

Review entrypoint for the stack services:

docker exec -it ee-stack bash
-->#$ /


  • Please do change your secure http password (admin port 22222) at first run of the ee-stack image:
    ee secure --auth

TODO for production site:

  • Mapping actual data volumes to host: MariaDB (/var/lib/mysql), WordPress (htdocs/html/php)
  • Split each stack service into its own container as practice advice for miro-services
Docker Pull Command