composer php - Laravel packages in Production -


i want make sure if understanding correct. when developing locally, cli, use composer bring in packages use app. these packages put in "vendor" directory.

now, vendor directory included in gitignore file won't pushed version control. however, when deploy app production, since vendor packages not version controlled, in cli (while ssh'd server) need run composer update. grab dependencies composer.lock file , install them on server.

consequently, when developing locally, if pull in new package, i'd have run composer update on server new package production.

please let me know if understanding of correct. thanks!

you don't want running composer update on production. want run composer install.

with composer update have possibility of upgrading packages using versions haven't tested them on. if need update dependencies can local , composer.lock file updated. lock file committed, on server running composer install install packages match versions in lock file keep consistent in environments.


Comments

Popular posts from this blog

SVG stroke-linecap doesn't work for circles in Firefox? -

routes - Laravel 4 Wildcard Routing to Different Controllers -

cross browser - XSLT namespace-alias Not Working in Firefox or Chrome -