From f6059890b1259f7aba4a301b4a049bacc7c35916 Mon Sep 17 00:00:00 2001 From: Jeff Turcotte Date: Thu, 21 Feb 2013 21:05:27 -0500 Subject: [PATCH 1/2] Satis configuration file description Better upfront description of what a Satis configuration file actually is. Was previously not clear the name didn't matter until further down. --- doc/articles/handling-private-packages-with-satis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/articles/handling-private-packages-with-satis.md b/doc/articles/handling-private-packages-with-satis.md index 18ce0725e..7aa959da6 100644 --- a/doc/articles/handling-private-packages-with-satis.md +++ b/doc/articles/handling-private-packages-with-satis.md @@ -13,7 +13,7 @@ your own. It basically acts as a micro-packagist. You can get it from For example let's assume you have a few packages you want to reuse across your company but don't really want to open-source. You would first define a Satis -configuration file, which is basically a stripped-down version of a +configuration, a json file with an arbitrary name that is basically a stripped-down version of a `composer.json` file. It contains a few repositories, and then you use the require key to say which packages it should dump in the static repository it creates, or use require-all to select all of them. From 6428aa1aa28833e3a551b2ece6d7ea631c70512c Mon Sep 17 00:00:00 2001 From: Jeff Turcotte Date: Fri, 22 Feb 2013 09:48:43 -0500 Subject: [PATCH 2/2] Further simplified Satis Config intro --- doc/articles/handling-private-packages-with-satis.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/doc/articles/handling-private-packages-with-satis.md b/doc/articles/handling-private-packages-with-satis.md index 7aa959da6..3436830fa 100644 --- a/doc/articles/handling-private-packages-with-satis.md +++ b/doc/articles/handling-private-packages-with-satis.md @@ -13,10 +13,8 @@ your own. It basically acts as a micro-packagist. You can get it from For example let's assume you have a few packages you want to reuse across your company but don't really want to open-source. You would first define a Satis -configuration, a json file with an arbitrary name that is basically a stripped-down version of a -`composer.json` file. It contains a few repositories, and then you use the require -key to say which packages it should dump in the static repository it creates, or -use require-all to select all of them. +configuration: a json file with an arbitrary name that lists your curated +[repositories](../05-repositories.md). Here is an example configuration, you see that it holds a few VCS repositories, but those could be any types of [repositories](../05-repositories.md). Then it