From b63cfb7b379df5a26927ea54adadceabd04a80fd Mon Sep 17 00:00:00 2001 From: JamesRezo Date: Fri, 27 Nov 2015 09:30:04 +0100 Subject: [PATCH] Other options --- doc/articles/handling-private-packages-with-satis.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/articles/handling-private-packages-with-satis.md b/doc/articles/handling-private-packages-with-satis.md index d6ba87a63..8ae789fb4 100644 --- a/doc/articles/handling-private-packages-with-satis.md +++ b/doc/articles/handling-private-packages-with-satis.md @@ -279,3 +279,10 @@ When searching for packages, satis will attempt to resolve all the required pack Therefore, if you are requiring a package from Packagist, you will need to define it in your `satis.json`. Dev dependencies are packaged only if the `require-dev-dependencies` parameter is set to true. + +### Other options + + * `output-dir`: optional, defines where to output the repository files + if not provided as an argument when calling the `build` command. + * `config`: optional, lets you define all config options from composer, except `archive-format` and `archive-dir` as the configuration is done through [archive](#downloads) instead. See + (http://getcomposer.org/doc/04-schema.md#config)