public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Replace toran

pull/6165/head
Jordi Boggiano 2017-02-10 13:32:08 +01:00
parent 07123715d6
commit 363bab90fa
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/faqs/why-can't-composer-load-repositories-recursively.md
View File

@ -8,8 +8,9 @@ Before going into details as to why this is like that, you have to understand
that the main use of custom VCS & package repositories is to temporarily try
some things, or use a fork of a project until your pull request is merged, etc.
You should not use them to keep track of private packages. For that you should
look into [setting up Satis](../articles/handling-private-packages-with-satis.md)
or getting a [Toran Proxy](https://toranproxy.com) license for your company.
rather look into [Private Packagist](https://packagist.com) which lets you
configure all your private packages in one place, and avoids the slow-downs
associated with inline VCS repositories.
There are three ways the dependency solver could work with custom repositories: