You can clone with
With the increasing amount of options, both related to projects and the system, it seems like relying on ENV vars will only cause pain in the very near future. Since Git pretty much nailed this by using a global gitconfig under the user home dir and a project-based git-config on the root of the project itself, I wonder if this exact model doesn't make sense for Composer too?
Some ideas came to mind:
autoupdate = true # auto self-update
prefersource = true # always prefer source
validateoninstall = true # always validate composer.json before executing the install command
assetsinstall = 'symlink'
What do you think?
Sounds interesting. But IMO if we would try to implement such "config" it should be first "project-based", later it could be pretty easy extended into "global" one.
We will need a ~/.composer dir sooner or later for caching stuff, so the config could go in there. Project config could just be .composer I guess, but I'm not sure if project config makes sense. Depends on what we consider config I guess.
I've updated the configuration to better indicate that the vendors config would possibly be configured as a section (like branch or mergetool). I see the project config only as a way to override the global config.
Add Config class and system-wide config management, fixes #513
This is now fixed, added three new tickets (#552, #553, #554) to expand on this feature.