From 9605fb17a3263a7d95124589e17bcee34df60200 Mon Sep 17 00:00:00 2001 From: Matthias Niess Date: Wed, 9 Mar 2022 17:34:17 +0100 Subject: [PATCH] The docker-compose.override.yml should not be ignored by default (#5838) While this file can be used for local overrides, that is not its only intended usage. E.g. a common setup would be like this: - *docker-compose.yml*: services shared across builds - *docker-compose.override.yml*: services only used in development - *docker-compose.production.yml*: configuration needed for building production images. Now for regular development you just need to run `docker-compose up --build` and only in you CI you would build and run for production by explicitly naming the yml files. TL;DR: Excluding docker-compose.override.yml seems to be a personal preference of someone and they should do that in their global .gitignore if the are so inclined. --- .gitignore | 1 - 1 file changed, 1 deletion(-) diff --git a/.gitignore b/.gitignore index eb003b01..bc67a663 100644 --- a/.gitignore +++ b/.gitignore @@ -6,7 +6,6 @@ .env .env.backup .phpunit.result.cache -docker-compose.override.yml Homestead.json Homestead.yaml npm-debug.log