Level 51
You have answer on this post
http://stackoverflow.com/a/33052243
And you should never run composer update in production.
Jul 4, 2016
8
Level 3
What is the difference between composer install and composer update?
I am sometimes confused with composer install and update.
Level 50
And you should never run composer update in production.
Actually you should, but should also run this song in the background while you do it ☺
3 likes
Level 52
And you should never run composer update in production.
Why ?
Level 3
@tomo_pongrac thanks
Level 17
Why ?
Because then your production site may be using different (newer) packages than your development site. The newer packages may break something.
Instead, run composer update in development and run your tests. Then, when you run composer install in production, you know your production site will be getting the exact same set of packages that you tested with your development site.
On a related note, never run your test suite in production.
Level 52
Because then your production site may be using different (newer) packages than your development site. The newer packages may break something.
In this case I can understand but for casual update it's ok.
Level 65
@MikeHopley That assumes you've got a separate code base for development. For simple sites I think this is fine (like upgrading WP on the fly). Always do a backup though.
1 like
Level 3
Composer install will install the packages from your composer.lock file Composer update will update/install the packages based on your composer.json file
Please or to participate in this conversation.