laravel/.gitignore
Matthias Niess 9605fb17a3
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.
2022-03-09 10:34:17 -06:00

15 lines
179 B
Plaintext

/node_modules
/public/hot
/public/storage
/storage/*.key
/vendor
.env
.env.backup
.phpunit.result.cache
Homestead.json
Homestead.yaml
npm-debug.log
yarn-error.log
/.idea
/.vscode