From 1b908d4f8073a0bdf9512dc97aba92b71d01ae8d Mon Sep 17 00:00:00 2001 From: Beau Simensen Date: Wed, 18 Jan 2012 22:54:59 -0800 Subject: [PATCH] Changing vendor bin configuration --- doc/faqs/vendor-bins.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/doc/faqs/vendor-bins.md b/doc/faqs/vendor-bins.md index 15be0f3f0..990e2b73d 100644 --- a/doc/faqs/vendor-bins.md +++ b/doc/faqs/vendor-bins.md @@ -86,3 +86,25 @@ of bins in a special way when run in a Windows environment: Packages that need to support workflows that may not include Composer are welcome to maintain custom `.bat` files. In this case, the package should **not** list the `.bat` file as a bin as it is not needed. + + +## Can vendor bins be installed somewhere other than vendor/bin? + +Yes, there are two ways that an alternate vendor bin location can be specified. + + * Setting the `vendor-dir` configuration setting in `composer.json` + * Setting the environment variable `COMPOSER_VENDOR_DIR` + +An example of the former looks like this: + +```json +{ + "config": { + "vendor-dir": "scripts" + } +} +``` + +Running `composer install` for this `composer.json` will result in +all of the vendor bins being installed in `scripts/` instead of +`vendor/bin/`. \ No newline at end of file