EasyEngine/easyengine

Use single mustache template to generate docker-compose.yml

Open

#1,193 opened on Aug 28, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)PHP (1,984 stars) (429 forks)batch import
good first issue

Description

Currently both site-command and site-wp-command has a seperate docker-compose.yml. This makes making changes and keeping them consistent harder.

We need to keep only single docker-compose.yml in any one repo (preferably easyengine as we already need it for global docker-compose.yml). Whenever we need to generate docker-compose.yml, we'll use that template.

Contributor guide

Tech stack
phpdocker
Domain
devops
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
docker compose basicsmustache templates
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue currently has two separate docker compose.yml files in site command and site wp command. Consolidate them into a single mustache template in the easyengine repository. Check the existing global docker compose.yml in easyengine for reference. The single template should generate the docker compose.yml dynamically. There is one comment on the issue; review it for any additional context or proposed approach.