laravel/laravel — Issue #290: Env modified bundle config locations
Author: sparksp
Created: 2012-01-30 11:15:02+00:00
State: open

So default config for bundles is simple, `{bundle}/config/{file}.php` but the env locations are within the bundle: `{bundle}/config/{env}/{file}.php`. I understand why it's in here, it's the easiest place to put them and it keeps it with the bundle, however I treat other people's bundles as **read-only**. So when I install someone else's bundle I don't go and change the code in there - this will also keep the git submodules clean.

In git submodules are recorded in a project based on their commit, when you make changes within a submodule it is marked as "-dirty" until the changes are committed. They should also be pushed otherwise you'll not be able to get them back if you clone the main repo again. When you decide to update the submodule in the future you want to avoid having changes in them so you would end up stashing your config tweaks, pulling changes, committing the main repo and then popping the config tweaks. The submodule (and main repo) will also always appear "dirty" :(

Suggestions:

* bundles/config/{env}/{bundle}/{file}.php
* application/config/{env}/{bundle}/{file}.php
* config/{env}/{bundle}/{file}.php