From 363bab90fa1f45a3801f012d5b544175dab816d8 Mon Sep 17 00:00:00 2001 From: Jordi Boggiano Date: Fri, 10 Feb 2017 13:32:08 +0100 Subject: [PATCH] Replace toran --- doc/faqs/why-can't-composer-load-repositories-recursively.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/faqs/why-can't-composer-load-repositories-recursively.md b/doc/faqs/why-can't-composer-load-repositories-recursively.md index 0ab44c7d2..56127f7dd 100644 --- a/doc/faqs/why-can't-composer-load-repositories-recursively.md +++ b/doc/faqs/why-can't-composer-load-repositories-recursively.md @@ -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: