Repository files navigation

A pretty simplified Docker Compose workflow that sets up a LEMP network of containers for local Laravel development. You can view the full article that inspired this repohere.

To get started, make sure you haveDocker 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 runningdocker-compose up -d --build site.

After that completes, follow the steps from thesrc/README.md file to get your Laravel project added in (or create a new blank one).

Bringing up the Docker Compose network withsite instead of just usingup, 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

Three additional containers are included that handle Composer, NPM, and Artisan commandswithout 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

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 amysql folder in the project root, alongside thenginx andsrc folders.
2. Under the mysql service in yourdocker-compose.yml file, add the following lines:

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