data # Directory linked to VirtualBox API
├─── build # Data used to build containers (i.e., DockerFile)
├─── conf # Configuration data used by services
├─── data # Raw data used by services
└─── log # Logs issued by services
- Docker;
- Docker Compose;
- Less time to prepare environment, more time to develop.
git clone https://gitlab.com/Creased/docker-webdev-env webdev-env
pushd webdev-env/
Build of containers based on docker-compose.yml:
docker-compose pull
docker-compose build
To get it up, please consider using:
docker-compose create
docker-compose start
docker-compose up
To get this setup ready, please make sure to fill-in your host file to catch these domains (see howtogeek):
- app.dev: Production web project;
- gitlab.dev: Git repositories;
- stackedit.dev: StackEdit WEB app;
- {lab.dev, local.dev}: Web projects laboratory.
Your host file should look like (depending to your system):
127.0.0.1 localhost local.dev gitlab.dev stackedit.dev lab.dev app.dev
When done, turn on your web browser and crawl:
- http://app.dev/: phpinfo() passed to PHP-FPM;
- http://app.dev/index.html: Static web page delivered directly by Nginx;
- http://app.dev/adminer/: Adminer authentication page to test MariaDB connection (default creds: admin-app:app-admin);
- http://gitlab.dev/: Gitlab-CE setup page proxified by Nginx;
- http://stackedit.dev/: StackEdit WEB app proxified by Nginx;
- http://lab.dev/: Projects list in laboratory.
docker-compose logs --follow
Template:
docker-compose exec SERVICE COMMAND
Example:
docker-compose exec db bash
Then you will be able to manage your configuration files, debug daemons and much more...