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

Add docs for diag command

pull/1769/head
Jordi Boggiano 2013-04-04 00:47:03 +02:00
parent 1060d015fb
commit 7740196b13
2 changed files with 14 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/03-cli.md
View File

@ -348,6 +348,14 @@ performance.
autoloader. This is recommended especially for production, but can take
a bit of time to run so it is currently not done by default.
## diag
If you think you found a bug, or something is behaving strangely, you might
want to run the `diag` command to perform automated checks for many common
problems.
$ php composer.phar diag
## help
To get more information about a certain command, just use `help`.

9
doc/articles/troubleshooting.md
View File

@ -7,13 +7,16 @@ This is a list of common pitfalls on using Composer, and how to avoid them.
## General
1. When facing any kind of problems using Composer, be sure to **work with the
1. Before asking anyone, run [`composer diag`](../03-cli.md#diag) to check
for common problems. If it all checks out, proceed to the next steps.
2. 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. Make sure you have no problems with your setup by running the installer's
3. Make sure you have no problems with your setup by running the installer's
checks via `curl -sS https://getcomposer.org/installer | php -- --check`.
3. Ensure you're **installing vendors straight from your `composer.json`** via
4. 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.