Makefiles to execute common tasks during development, but you can also use standard Docker commands to control your stack.
make targets are just shorthands for lengthy Docker commands.
TODO: Link "Backend", "Frontend"
To see all available targets run
After the initial
.env configuration, for first initial setup run
You can also chain single targets
make setup up open bash
docker-compose commands against your current stack
docker-compose ps docker-compose logs
Makefiles for a different folder i.e. for managing an isolated test-stack
cd tests make all make run-tests
You can find information in the testing section.
maketargets are run on the stack as
docker-composewithout additional parameters.
:bulb: To do a dry-run for a command you can use the
make -n all
:warning: removing containers, i.e. with
make cleanremoves also data stored only in the container, you can use host-volumes for persisting data during development
Makevs. Docker commands
You can create a new CLI-container bash with
docker-compose run --rm php bash
Alternatively you can also execute a bash within a running container
docker-compose exec php bash
docker exec -it myapp_php_1 bash
Setup application with demo data and default user password
docker-compose run --rm \ -e APP_ADMIN_PASSWORD=admin1 \ -e APP_MIGRATION_LOOKUP=@app/migrations/demo-data \ php yii app/setup
TODO: link tutorials
make -n all
docker-compose build --pull
docker-compose up -d
docker-compose run --rm php yii app/setup
xdg-open http://localhost:21548 &>/dev/null
Help us to improve the documentation, fork this page.