Open tristanlins opened 11 years ago
Additional repositories have currently to be defined in the composer.json of a project itself or in the composer system config. If we stick to our forked composer, this can of course be altered in any way we like (and I want to add: with minimal effort).
@discordier i would put this as a service in our integration (what !composer) is, not into the fork
@discordier I want do modify the local composer.json, because extra repositories belongs to the local project. PS: The editor should part of the UI (our client), not the fork.
I would suggest a new feature to the client interface: A repository manager/editor
The manager should make it possible to:
The import and export make it easy to simply share developer repositories AND protected / non-public repositories. The spec should contain all the necessary informations like username+password or client certificate.