Magento 2.1.1 (with sample data) Docker dev environment which includes:
- PHP 7.0.x - Will use latest FPM alpine base image
- Nginx
- Self signed SSL (separate nginx container for ssl offloading, this is by default. Using dock-cli, it can be accessed via dnsdock alias: https://m2.docker)
- Varnish 4.x
- MariaDB
- Redis
- Node 6.7.x for frontend dependencies
- ELK stack for logs
- Mailcatcher (accessed via mailcatcher.docker)
- Selenium for Behat tests
This setup utilises the dock-cli setup, which provides a DNSDock container, docker-machine and DNS management for the host machine. If you would like to use Docker for Mac, this setup would need some slight tweaking, such as using a combination of dnsmasq and nginx proxy containers
I recommend using docker-machine-nfs:
docker-machine-nfs $DOCKER_MACHINE_NAME --shared-folder=/Users/<username>
###Installation
dock-cli start OR docker-compose up -d
docker-compose exec php ./bin/composer install
Copy the sample env.php over for some suggested settings (e.g use redis for session storage)
cp docker/env-sample.php app/etc/env.php
Run Magento 2 CLI installation command with example settings:
docker-compose exec php php ./bin/magento setup:install --admin-firstname=admin --admin-lastname=admin [email protected] --admin-user=admin --admin-password=123123pass --base-url=https://m2.docker/ --base-url-secure=https://m2.docker/ --use-secure=1 --use-secure-admin=1 --db-password=magento2 --db-host=mariadb.docker --db-name=magento2 --db-user=magento2 --language=en_GB --currency=GBP --timezone=Europe/London --use-sample-data
# you might have to chmod +x ./bin/magento if you get permission errors
This will install a Magento 2 instance with sample data, if you don't want this data then remove the flag --use-sample-data
Varnish can be turned by selecting the 'Varnish Cache' option via the admin dashboard:
Stores > Configuration > Advanced > System > Full Page Cache > Caching Application
You can then clear the cache:
docker-compose exec php ./bin/magento cache:clean
To view the status of the containers:
dock-cli ps or docker-compose ps -q
To start a shell in the web container/service, for debugging purposes:
docker-compose exec web sh
There can be benefits in generating an optimized autoloader.
docker-compose exec php ./bin/composer dump-autoload -o
You can run behat tests:
docker-compose exec php ./bin/behat
To build the frontend dependencies, you can use the node container (--rm flag to remove containers once completed, to keep setup clean)
docker-compose run --rm node npm install
docker-compose run --rm node grunt <task>
Credit to Mage Inferno for some inspiration and ideas on how all of this could be down 👍