From 03ecf00f7a4e14c049e41bb111430877313449b9 Mon Sep 17 00:00:00 2001 From: Attila Szeremi Date: Thu, 10 Dec 2020 14:32:49 +0100 Subject: [PATCH] Gitignore docker-compose.override.yml (#5487) Docker allows for you to override parts of `docker-compose.yml` locally with the help of a `docker-compose.override.yml` file: https://docs.docker.com/compose/extends/#understanding-multiple-compose-files I propose to have this file ignored by default for new projects, similarly to how `.env` is ignored to be able to override default configuration (locally). Example use case: Someone might want to use Laravel Sail, but would have multiple Laravel projects running in MySQL and would like to run a single MySQL server for each project and have a way to be able to override docker-compose to make that happen. Or maybe just in general they want to add a new service that they want to run only for themselves, and not for colleagues. --- .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index 0f7df0fb..0ae59f0b 100644 --- a/.gitignore +++ b/.gitignore @@ -6,6 +6,7 @@ .env .env.backup .phpunit.result.cache +docker-compose.override.yml Homestead.json Homestead.yaml npm-debug.log