docker-compose-Bjornstad2

A simplified Docker Compose workflow that sets up a BEMP network of containers for local development.

Usage

To get started, make sure you have Docker installed on your system, and then clone this repository.

Next, navigate in your terminal to the directory you cloned this, and spin up the containers for the web server by running docker-compose up -build -d

Bringing up the Docker Compose network with site instead of just using up, ensures that only our site's containers are brought up at the start, instead of all of the command containers as well. The following are built for our web server, with their exposed ports detailed:

• nginx - :8080
• mysql - :3306
• php - :9000
• phpmyadmin - :5000

Three additional containers are included that handle Composer, NPM, and Artisan commands without having to have these platforms installed on your local computer. Use the following command examples from your project root, modifying them to fit your particular use case.

• docker-compose run --rm composer update
• docker-compose run --rm npm run dev
• docker-compose run --rm artisan migrate

Persistent MySQL Storage

By default, whenever you bring down the Docker network, your MySQL data will be removed after the containers are destroyed. If you would like to have persistent data that remains after bringing containers down and back up, do the following:

1. Create a mysql folder in the project root, alongside the nginx and src folders.
2. Under the mysql service in your docker-compose.yml file, add the following lines:

volumes:
  - ./mysql:/var/lib/mysql

Issues

Server Error 500

exec into php container: docker exec -ti php sh

install dependencies: composer install

run node install: docker run --rm node install

Unable to access storage

exec into php container: docker exec -ti php sh

change ownership: chown -R www-data: storage chown -R www-data: bootstrap/cache