Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/kojiromike/docker-magento
A Magento Development Environment Made of Docker Containers
https://github.com/kojiromike/docker-magento
Last synced: 25 days ago
JSON representation
A Magento Development Environment Made of Docker Containers
- Host: GitHub
- URL: https://github.com/kojiromike/docker-magento
- Owner: kojiromike
- License: mit
- Archived: true
- Created: 2014-10-02T21:09:50.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2016-09-27T13:36:43.000Z (about 8 years ago)
- Last Synced: 2024-08-03T18:16:26.100Z (4 months ago)
- Language: Nginx
- Homepage:
- Size: 360 KB
- Stars: 94
- Watchers: 7
- Forks: 40
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
- awesome-magento - Docker Magento - Another Docker image for Magento. (Docker Images / Full Page Caching)
README
# Docker for Magento 1 Extension Development
## Tl;dr How do I use this?
1. Clone it.
1. Type `docker-compose up -d`.
1. [Install a Magento](tools/README.md)
1. [Mount your file share.](#how-do-i-use-the-file-share-container)
1. Develop
1. Profit!!!
## How should we build this?
Normally with Magento you get a plain LAMP stack; Apache with `mod_php`.
That's fine, but since Docker containers are so nicely isolated,
I want this approach:
--------------------- ------------- -------
| HTTPD/FastCGI Proxy | <-> | FastCGI PHP | <-> | MySQL |
--------------------- ------------- -------
\ /
------------ -----------------------
| File Share | <-> | Data Volume Container |
------------ -----------------------
Separating the HTTP server from the PHP process gives us a more true-to-form
web architecture where the web application server is distinct from the
web server. It means we can scale and reconfigure the different server layers
independently. It means we can destroy or replace a component without
destroying the other containers or their data.
## What do we need to get started?
1. A container for the HTTPD. We'll build from `nginx` and try to configure it for FastCGI.
1. A container for MySQL. `mysql:5` should do.
1. A container for PHP. We'll use the official Docker PHP images with additional extensions Magento requires.
1. A container for data volumes. The simplest docker container needs a no-op executable like `true` and some files. We'll start from `scratch` and add on from there.
1. A container for humans to touch data volumes.
## How do we set it up?
Docker has a nice tool for orchestrating multiple containers for dev
environments called [Compose](http://docs.docker.com/compose/). I defined a
docker-compose file that builds and connects the aforementioned containers
from its Dockerfile in each of the directories named after the service:
_nginx_, _php_, _mysql_, _data_, _fs_. So just run `docker-compose up`.
## How should I access the web server?
In Docker, the exposed ports run on the Docker host. If you're using
`boot2docker`, you can get the `ip` with `boot2docker ip`. The included
`browse` command should be a shortcut for OS X users.
## How do I get to my data?
How Docker actually houses live data is a little confusing, particularly if
you're viewing it from a workstation instead of the Docker daemon host, where
the volume actually resides. It might help to review
[Docker's own documentation](https://docs.docker.com/userguide/dockervolumes/)
on the subject. Anyway, the tl;dr version is _that's what the file share
container is for_.
### How do I use the file share container?
The file share container creates a CIFS share for the Magento directory.
#### OS X
```sh
mkdir -p
mount_smbfs -N //guest@/magento_data_1
```
#### Windows
```
net use : \\guest@\magento_data_1
```
#### Linux
Similar to the OS X one, probably uses `mount -t cifs`. I didn't try it.
Alternatively, you can run docker directly on the linux machine and access
its volumes directly.
(The above commands assume the file share container name is `magento_data_1`.
That will be true if you work in a directory named `magento`. For how to make
this work with other directory names, see [my note on container names](https://github.com/kojiromike/docker-magento/tree/master/tools#note-container-names) over at the tools README.)
## Known issues
- Speed: The CIFS share is a little slow. I tried to set up an NFS share, but
couldn't get it working. Taking pull requests for faster shares.
- Disappearing data: Don't panic - if you try something like `docker cp` or
`docker export` on the _data_ container it will appear unchanged. The data is
safe (in fact, the data is still on the host machine even if you delete the
container, as long as you don't `docker rm -v` it.) Try something like
```
docker run --volumes-from magento_data_1 debian tar x /srv/magento > export.tar
```
to get a snapshot of your data. (Although it might be easier just to use the
share.)