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.
This enables the sqlite `foreign_key_constraints` option that was introduced with laravel/framework#26298 for all new installs.
The env variable DB_FOREIGN_KEYS was added to make it easier to handle this in testing (e.g. via phpunit.xml).
Matthias Niess