We are using
docker-compose to provide as consistent a local development environment as possible, in accordance with 12factor development principles.
Firstly, check you have all the requirements on your system. For Linux users, these are either preinstalled or available through your distribution's package manager.
make - Instructions for installing make vary, for OSX users
xcode-select --install might work
docker-compose - This should be installed along with docker on OSX and Windows
envsubst - This should be pre-installed on most Linux distributions
The first time you'll need to follow the steps below, in order to clone this repo and build the containers.
# Clone the repositorygit clone https://github.com/greenpeace/planet4-docker-compose# Navigate to new directorycd planet4-docker-compose# Build containers, start and configure the applicationmake dev
If you want the application repositories to be cloned using ssh protocol, instead of https, you can use a variable:
GIT_PROTO="ssh" make dev
If you want to run docker-compose commands directly:
# Set your shell environment variables correctlyeval $(make env)# View status of containersdocker-compose ps# View log outputdocker-compose logs -f
On first launch, the container bootstraps the installation with composer then after a few minutes all services will be ready and responding to requests.
When the terminal is finished, and you see the line 'ready', navigate to www.planet4.test.
It's not necessary to re-run
make dev each time you wish to start the local development environment. To start containers on subsequent runs, use:
If the current setup is too heavy for your machine, there is a lighter version that skips creating some of the containers. Keep in mind though that this leaves out PhpMyAdmin, ElasticHQ and Selenium containers, so it would be harder to debug things.
To use it, you need to set the relevant environmental variable. For instance:
DOCKER_COMPOSE_FILE="docker-compose.light.yml" make run
To view the output of running containers:
eval $(make env)docker-compose logs
If at any point the install process fails, with Composer showing a message such as
file could not be downloaded (HTTP/1.1 404 Not Found), this is a transient network error and re-running the install should fix the issue.
To stop all the containers just run:
To update all containers, run:
By default, the Wordpress application is bind-mounted at:
All planet4 code will be under the Wordpress' content folder:
Backend administrator login is available at www.planet4.test/wp-admin/.
Login username is
admin and the password is