The best way to update the composer dependency in production is by running "composer update" first on your local development. By doing so the "composer.lock" file will be updated and when you have a check for any breaking changes, it's time to push to the server and then run "composer install".
Below are the steps to do so:
Below are the steps to do so:
- "composer update" on the local development.
- check for any breaking changes.
- commit the "composer.lock" file and push to git/production.
- run "composer install" from the production server.
By ensuring that everything is running fine in the local development, it will now be safe to run the command in the production environment.
Leave a reply