Feeling Lucky
[#48] - Suggest "composer install" instead of "update"
- Closed
- 30 May 2015
- Medium
- Build: master
- # 48
- Diff
- zanardigit:master
- Error continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error Details
User tests: Successful: Unsuccessful:
"composer update" is something you should only do as project maintainer, when you want to check for newer versions of your dependencies, or after you changed anything in your composer.json file (i.e. added / modified / removed dependencies). This command not only will download dependencies, but also create a new "composer.lock" file.
On all other cases (deployment, testing) it is best to use "composer install" which only reads the "composer.lock" file. In this way, you are sure that every machine gets the exact same version. And as a nice bonus is much faster than the "composer.update" command :-)
mbabker
- 
zero-24
- | Milestone |
Added: 3.4.1 |
||