|
9 anni fa | |
---|---|---|
README.md | 9 anni fa | |
docker-compose.yml | 9 anni fa |
This docker-compose.yml file is provided by Mage Inferno
Author: Mark Shust mark.shust@mageinferno.com
View our Docker Hub images at https://hub.docker.com/u/mageinferno/
This file is provided as an example development environment using Mage Inferno Magento 2 Docker Images. We suggest to supply specific version releases as this will maintain a consistent development environment (nginx:1.9 vs. nginx).
Create a new folder to house your project, ex: ~/Sites/mysite
then, please your docker-compose.yml file within this directory.
Setup will create a new directory at ~/Sites/mysite/src
which will hold all of the source files for Magento 2.
app:
image: mageinferno/magento2-nginx:1.9
links:
- php-fpm
- db
volumes_from:
- appdata
environment:
- VIRTUAL_HOST=mysite.docker
appdata:
image: tianon/true
volumes:
- ./src:/src
- ~/.composer:/root/.composer
"php-fpm":
image: mageinferno/magento2-php:7.0-fpm
links:
- db
volumes_from:
- appdata
db:
image: mariadb:10.0
ports:
- "8001:3306"
volumes_from:
- dbdata
environment:
- MYSQL_ROOT_PASSWORD=magento2
- MYSQL_DATABASE=magento2
- MYSQL_USER=magento2
- MYSQL_PASSWORD=magento2
dbdata:
image: tianon/true
volumes:
- /var/lib/mysql
setup:
image: mageinferno/magento2-setup:2.0
links:
- db
volumes_from:
- appdata
environment:
- M2SETUP_DB_HOST=db
- M2SETUP_DB_NAME=magento2
- M2SETUP_DB_USER=magento2
- M2SETUP_DB_PASSWORD=magento2
- M2SETUP_BASE_URL=http://mysite.docker/
- M2SETUP_ADMIN_FIRSTNAME=Admin
- M2SETUP_ADMIN_LASTNAME=User
- M2SETUP_ADMIN_EMAIL=dummy@gmail.com
- M2SETUP_ADMIN_USER=magento2
- M2SETUP_ADMIN_PASSWORD=magento2
- M2SETUP_USE_SAMPLE_DATA=true
This setup attaches the ~/.composer
directory from the host machine. For fully automated setup, please first setup a GitHub Personal Access Token for Composer (before running setup) by visiting https://github.com/settings/tokens/new?scopes=repo&description=Composer.
You'll also need to retrieve your Magento development keys. Please see http://devdocs.magento.com/guides/v2.0/install-gde/prereq/connect-auth.html for more details.
After both sets of keys are retrieved, place your auth token on your host machine at ~/.composer/auth.json
with the following contents, like so:
{
"http-basic": {
"repo.magento.com": {
"username": "MAGENTO_PUBLIC_KEY",
"password": "MAGENTO_PRIVATE_KEY"
}
},
"github-oauth": {
"github.com": "GITHUB_ACCESS_TOKEN"
}
}
If you don't want to use Composer or setup the auth keys above, no worries. Magento provides a complete Magento 2 archive at http://devdocs.magento.com/guides/v2.0/install-gde/prereq/zip_install.html. We decided to use this method for a very quick installation.
Just specify the full version (2.x.x), for example 2.0.0
for an install without sample data, or 2.0.0-sd
for an install with sample data.
Note that the abbreviated (2.x) version, for example 2.0
, is reserved for the Composer install process.
Before running Magento 2, you must download the source code, install composer dependencies, and execute the Magento installer script. Luckily, Mage Inferno makes this easy for you.
The following environment variables can be set for setup:
- M2SETUP_DB_HOST=db
- M2SETUP_DB_NAME=magento2
- M2SETUP_DB_USER=magento2
- M2SETUP_DB_PASSWORD=magento2
- M2SETUP_BASE_URL=http://mysite.docker/
- M2SETUP_ADMIN_FIRSTNAME=Admin
- M2SETUP_ADMIN_LASTNAME=User
- M2SETUP_ADMIN_EMAIL=dummy@gmail.com
- M2SETUP_ADMIN_USER=magento2
- M2SETUP_ADMIN_PASSWORD=magento2
- M2SETUP_USE_SAMPLE_DATA=true
Our setup script uses these variables to determine how to setup your store. Everything is pretty self-explanatory. The M2_USE_SAMPLE_DATA
variable is only used with Composer-based installs.
To run setup, execute the following command from your project directory (~/Sites/mysite
), which creates a one-off throw away container that sets up Magento 2 for you.
docker-compose run --rm setup
Note that setup will take around 30 minutes to complete. A vast majority of this time is from downloading Composer dependencies, and installing sample data (configurable products, specifically). Setting M2SETUP_USE_SAMPLE_DATA
to false will expedite the install process by skipping the installation of sample data.
This install will mount the src
directory from your host machine to the Docker container (ex: ~/Sites/mysite/src
). Note that the persistancy comes from your host machine, so you may terminate running nginx/php containers and start them back up, and your data will remain. The appdata
definition in the docker-compose.yml file is mainly there so we only have to define the relation in one place in the file, instead of it being defined multiple times.
For MySQL, the mysqldata
container runs from the tianon/true
volume. This makes a persistent Docker volume, however be aware that removing this container will remove all of your MySQL data (aka your database). Even though it appears as exited/stopped when running docker ps -a
, be sure not to remove this container, as your MySQL data will truly go away if you remove it.
This docker-compose file is catered to Dinghy, which uses it's own DNS Server and HTTP Proxy. Notice the VIRTUAL_HOST=mysite.docker
definition for the app
container. Dinghy uses this to create an HTTP Proxy, so your site can be access at http://mysite.docker. Note that all virtual names must end in .docker
for proper DNS resolution by Dinghy.