Skip to content
Docker development environment for staging Magento 1 & Magento 2 on Alpine 3.6
Shell Dockerfile Makefile VCL
Branch: master
Clone or download
Latest commit 42a6a49 Apr 12, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
dist Fixed GH-3 Aug 15, 2018
docs/images Version 1.0.0 Released Aug 3, 2018
src Fixed GH-7 Apr 12, 2019
.gitattributes Version 1.0.0 Released Aug 3, 2018
.gitignore Version 1.0.0 Released Aug 3, 2018
.travis.yml Changed build system & added CI/CD using Travis-CI Oct 5, 2018
LICENSE.md Version 1.0.0 Released Aug 3, 2018
Makefile Changed build system & added CI/CD using Travis-CI Oct 5, 2018
README.md Fixed GH-7 Apr 12, 2019

README.md

Docker Magento Alpine

Docker development environment for staging Magento 1 & Magento 2 on Alpine 3.6

Disclaimer

The docker containers within this repository were build for development purposes only and should NOT be used in production. This product is licensed under the MIT LICENSE and comes with no warranty, use at your own risk.

Supported tags and respective Dockerfile links

Getting Started

Using shared volumes on MacOS with Docker is painfully slow. That is why we use docker-sync for sharing volumes with and between docker containers. While this solution has a slightly longer initial up-time, it makes up for it when the containers are started and initially synced. We also use docker-compose to run our docker containers because of it's simplicity. Sample docker-compose files for Magento 1 and Magento 2 can be found in the dist directory. Similarly, there is a docker-sync.yml file that can be used alongside either configuration. Assuming that your Magento installation lives in public_html of your project folder, and the appropriate docker-compose.yml and docker-sync.yml files are found in the same directory, then you can start docker-sync and run the docker containers using the following sequence of commands:

docker-sync start
docker-compose up -d

Shutting them down is just as easy:

docker-compose down
docker-sync stop
docker-sync clean # Only if not starting again

Environmental Variables

All docker images, except for the php-cli containers, have the ability to tail their container's relevant logs if the VERBOSE=true flag is passed as an environmental variable. Passing it to the container is optional since by default VERBOSE=false. It is explicitly stated within the sample docker-compose.yml file for documentation purposes only. Please also note that you will only be able to see the verbose output of these containers if you run docker-compose without the detach flag, i.e. docker-compose up.

mysql

Since we build off of the mysql:5.7 image, the environment variables will look the same. One exeption is that we use MYSQL_USER_NAME instead of MYSQL_USER and MYSQL_USER_PASSWORD instead of MYSQL_PASSWORD. This is for backwards compatibility purposes. A full list of environment variables can be found here.

nginx

When NGINX starts, it copies the appropriate configuration file so it can be used. This configuration file is determined by the environment variable below. If no variable is passed then the below value is set.

  • MAGENTO_VERSION=2

Build System

Building our docker images is easy. We use a simple Makefile to manage building and publishing our docker images. As part of our CI/CD pipeline, we use Travis-CI to build our docker images on every push to the master branch. If the build process is successfull, then those new images will be pushed to docker hub. Please note that pull requests are not built automatically to avoid automated pushes to docker hub. Below are all the commands that are implemented within our build system:

  • make build_all: build all docker images that are found under src directory
  • make build <tag>: build specific image by passing the tag name as a parameter
  • make publish_all: push all docker images that have a folder in src
  • make publish <tag>: push specific image by passing the tag name as a parameter

Issues / Feature Requests

If any issues come up or any feature are requested, please feel free to open up an issue through Github. For all other inquiries, feel free to email us at development@jetrails.com.

You can’t perform that action at this time.