Skip to content
This repository

.composer/config for configuration options #513

Closed
ruimarinho opened this Issue March 29, 2012 · 4 comments

3 participants

Rui Marinho Jordi Boggiano Joseph Bielawski
Rui Marinho

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:

// ~/.composer/config

[core]
  autoupdate = true # auto self-update
  prefersource = true # always prefer source
  validateoninstall = true # always validate composer.json before executing the install command

[package "symfony/symfony"]
  assetsinstall = 'symlink'

What do you think?

Joseph Bielawski

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.

Jordi Boggiano
Owner

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.

Rui Marinho

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.

Jordi Boggiano Seldaek closed this in e638182 April 09, 2012
Jordi Boggiano
Owner

This is now fixed, added three new tickets (#552, #553, #554) to expand on this feature.

Felix Jodoin felixalias referenced this issue from a commit December 17, 2012
Commit has since been removed from the repository and is no longer available.
Felix Jodoin felixalias referenced this issue from a commit December 17, 2012
Commit has since been removed from the repository and is no longer available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.