joomla
/
weblinks
mirror of https://github.com/joomla-extensions/weblinks.git
30
1
Fork 0
Code Issues Releases Activity

Suggest "composer install" instead of "update" 

"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 :-)
This commit is contained in:
zanardigit 2015-05-30 17:15:29 +02:00
parent d25d3ff034
commit fe9edb142f
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -8,7 +8,7 @@ To prepare the system tests (Selenium) to be run in your local machine you are a
To run the tests please execute the following commands (for the moment only working in Linux and MacOS, for more information see: https://docs.joomla.org/Testing_Joomla_Extensions_with_Codeception):
```bash
$ composer update
$ composer install
$ vendor/bin/robo
$ vendor/bin/robo test:acceptance
```