Everything runs w/ docker-compose, which we spin up as a docker container. For now we have a base docker-compose.yml file and then override it with a second, stack-specific file, sort of like this:
All the PHP utils for this live in NorthStack\NorthStackClient\Docker. The classes in NorthStack\NorthStackClient\Docker\Action are the API that is exposed to our symfony commands. Each one has an idea about what docker-compose command it's supposed to run, whether to watch stdout/stderr, how to handle ctrl+c, how to tear down, etc.
WordPress management is pretty basic at the moment. There's a bash script that lives at /docker/images/wordpress/wordpress-init that handles installation and updating the admin user, siteurl, etc.
Okay there's a lot here.
Everything runs w/ docker-compose, which we spin up as a docker container. For now we have a base
docker-compose.ymlfile and then override it with a second, stack-specific file, sort of like this:All the PHP utils for this live in
NorthStack\NorthStackClient\Docker. The classes inNorthStack\NorthStackClient\Docker\Actionare the API that is exposed to our symfony commands. Each one has an idea about what docker-compose command it's supposed to run, whether to watch stdout/stderr, how to handle ctrl+c, how to tear down, etc.WordPress management is pretty basic at the moment. There's a bash script that lives at
/docker/images/wordpress/wordpress-initthat handles installation and updating the admin user, siteurl, etc.