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

Add toran to docs besides satis

pull/3271/head
Jordi Boggiano 2014-09-10 16:05:11 +01:00
parent a8adbfeb9f
commit 0e409a159c
2 changed files with 15 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/articles/handling-private-packages-with-satis.md
View File

@ -2,13 +2,21 @@
tagline: Host your own composer repository tagline: Host your own composer repository
--> -->
# Handling private packages with Satis # Handling private packages with Satis or Toran Proxy
Satis is a static `composer` repository generator. It is a bit like an ultra- # Toran Proxy
lightweight, static file-based version of packagist and can be used to host the
metadata of your company's private packages, or your own. It basically acts as [Toran Proxy](https://toranproxy.com/) is a commercial alternative to Satis offering professional support as well as a web UI to manage everything and a better integration with Composer.
a micro-packagist. You can get it from
[GitHub](http://github.com/composer/satis) or install via CLI: Toran's revenue is also used to pay for Composer and Packagist development and hosting so using it is a good way to support open source financially. You can find more information about how to set it up and use it on the [Toran Proxy](https://toranproxy.com/) website.
# Satis
Satis on the other hand is open source but only a a static `composer`
repository generator. It is a bit like an ultra-lightweight, static file-based
version of packagist and can be used to host the metadata of your company's
private packages, or your own. You can get it from [GitHub](http://github.com/composer/satis)
or install via CLI:
`php composer.phar create-project composer/satis --stability=dev --keep-vcs`. `php composer.phar create-project composer/satis --stability=dev --keep-vcs`.
## Setup ## Setup

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

@ -9,7 +9,7 @@ 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. 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 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) look into [setting up Satis](../articles/handling-private-packages-with-satis.md)
for your company or even for yourself. or getting a [Toran Proxy](https://toranproxy.com) license for your company.
There are three ways the dependency solver could work with custom repositories: There are three ways the dependency solver could work with custom repositories: