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

n 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

Riadh Rahmi

Senior Web Developer PHP/Drupal & Laravel

I am a senior web developer, I have experience in planning and developing large scale dynamic web solutions especially in Drupal & Laravel.

Recent comments

Recent content

Create paragraphs and attach to node programmatically in drupal 10

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

Provide token for media entities in Drupal 8 & 9

Create custom image token in drupal 8 & 9

How To Create A Custom Token In Drupal 8 & 9

How To Use Batch API in Drupal 8 & 9

How to use Batch API to do heavy processing in Drupal 8 & 9

Disable cache for a block in Drupal 8

Create and Apply Patches using GIT DIFF and APPLY

How to change canonical URL programmatically in drupal 8 & 9

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

Programmatically update an entity reference field 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