DOCKER FOR MAC VAGRANT HOW TO
DOCKER FOR MAC VAGRANT UPDATE

PHP (in my case), the database and the web server were all installed natively. In the dark ages, my usual set up for development of LAMP web applications was to test locally on my machine.

make your dev environment different from production keeping it as simple and straight forward as you can so developers won't feel the friction induced by using new tools.

make your dev environment replicate exactly your production environment.

In my view there are two ways to do things: You are asking the right questions but there is no answer that fit all situations. Having a Vagrantfile that provision a VM with docker is really easy with just shell provisioning IMHO puppet/chef/. There is no point going through setting up puppet correctly for your dev environment if all that work won't be used for the production environment. The best practice is to operate on your dev environment the same way you will operate on your production environment. Is it a good idea to use Puppet to create and manage the Docker containers, both for the development server and production server? Regarding backups, take a look at the docker user guide where everything you need to know in regards with volumes is detailed. If you want to easily access the data used by your containers, mounting a directory on the docker host is the way to go. There are different ways to work with volumes: you can mount a directory from the docker host to a container volume, or you can have data volume containers, or named volumes.Дocker volumes are an important concept and it is worthwhile to take the time to master them. What about the data they write that I don't want to loose?Дocker has a thing called volume to allow data to be written on a filesystem out of the container.

DOCKER FOR MAC VAGRANT UPDATE

If those apps need to share sessions make sure sessions are stored in database or on a docker volume that is accessible to all.Дocker containers seem to be designed to be replaceable rather than me having to update the software inside them. When I talk about parts of the web application, I mean things like, , etc. Take a look at supervisor or phusion/baseimage. A container from such an image would have to run multiple processes.

For a dev environment and if you use multiple containers, I would advise to use docker-compose.ДЄnother path is to build a docker image that is the closest to your production machine (assuming you have only one machine) which would run the database, the web server and php. On the other hand you have to link them together to allow them to interact. The docker hub provides ready to go containers for php, databases, etc and it is easy to use them. Else just use the docker containers the easiest way you can. If you will be using docker in production, then try to run your docker containers in your dev environment as they will be in production. There is no correct answer to that question.

Should there be separate Docker containers for the web server (such as Apache), the database server (such as MySQL) and each part of the web application?

DOCKER FOR MAC VAGRANT HOW TO

How to develop a LAMP web application using Docker, Puppet and Vagrant?

Docker for mac vagrant