Why should I never run 'composer update' in production | CodimTh

Please Disable Your Browser Adblock Extension for our site and Refresh This Page!

our ads are user friendly, we do not serve popup ads. We serve responsible ads!

Web tips, snippets & code sharing

On October 23, 2020 . By CodimTh

Category:

Not so much about Laravel, but... Never run composer update on production, it's slow and will "break" repository. Always run composer update locally on your computer, commit new composer.lock to the repository, and run composer install on server.

Tags :

Laravel Laravel tutoriel Tips Laravel

Comments

Add new comment

Recent comments

Recent content

How to Create a Custom Field Formatter in Drupal 8 & 9

Disable cache for a block in Drupal 8

Dependent select dropdowns using #ajax in node add/edit form drupal 8 & 9

Programmatically update an entity reference field in Drupal 8 & 9

How to change canonical URL programmatically in drupal 8 & 9

How To pass parameter from node to webform with custom token In Drupal 8 & 9

How to create media entities and attach them to paragraphs in Drupal 8 & 9

How to attach paragraphs to node programmatically in drupal 8 & 9

How to create custom contextual links programmatically in drupal 8 & 9

How to add a html field to a form in drupal 8 & 9

How to redirect an anonymous user to the login form after a 403 error in Drupal 8 & 9

How to redirect anonymous user in Drupal 8 & 9

How to get all vocabularies in drupal 8 & 9

How to create custom local actions programmatically in drupal 8 & 9

How to add open graph meta tags programmatically in drupal 8 & 9

If you need some help or you search a Drupal freelancer don't hesitate to contact us.

All the content is FREE but I still need your help