From e85ca1ed945cadd46ee17c5fd67f8876735eb8e6 Mon Sep 17 00:00:00 2001 From: Jordi Boggiano Date: Tue, 30 Oct 2012 12:54:53 +0100 Subject: [PATCH] Add --check to troubleshooting docs --- doc/articles/troubleshooting.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/articles/troubleshooting.md b/doc/articles/troubleshooting.md index 16cfb8ebc..23a30fa6f 100644 --- a/doc/articles/troubleshooting.md +++ b/doc/articles/troubleshooting.md @@ -10,7 +10,10 @@ This is a list of common pitfalls on using Composer, and how to avoid them. 1. When facing any kind of problems using Composer, be sure to **work with the latest version**. See [self-update](../03-cli.md#self-update) for details. -2. Ensure you're **installing vendors straight from your `composer.json`** via +2. Make sure you have no problems with your setup by running the installer's + checks via `curl -s https://getcomposer.org/installer | php -- --check`. + +3. Ensure you're **installing vendors straight from your `composer.json`** via `rm -rf vendor && composer update -v` when troubleshooting, excluding any possible interferences with existing vendor installations or `composer.lock` entries.