Cpanel composer update kill

The "Killed" message usually means your process consumed too much memory, so you may simply need to add more memory to your system if possible. At the time of writing this answer, I've had to increase my virtual machine's memory to at least 768MB in order to get composer update to work in some situations.

However, if you're doing this on a live server, you shouldn't be using composer update at all. What you should instead do is:

Run composer update in a local environment (such as directly on your physical laptop/desktop, or a docker container/VM running on your laptop/desktop) where memory limitations shouldn't be as severe.
Upload or git push the composer.lock file.
Run composer install on the live server.
composer install will then read from the .lock file, fetching the exact same versions every time rather than finding the latest versions of every package. This makes your app less likely to break, and composer uses less memory.

Source: stackoverflow.com

Similar codes

0 vote210 views3 answers
@parent laravel
PHP
-1 vote212 views1 answer
Echo in console command laravel
PHP Laravel
1 vote255 views2 answers
Show php modules installed
PHP
0 vote186 views1 answer
Ubuntu add phpstorm to launcher
PHP
0 vote186 views1 answer
Symfony\Component\HttpKernel\Exception\NotFoundHttpException: POST http://localhost/post
PHP
1 vote179 views1 answer
Add a year php
PHP
10 votes194 views6 answers
Format time laravel
PHP
0 vote185 views2 answers
Sorting sql query array by column key php
PHP
0 vote201 views1 answer
Cf7 first_as_label
PHP
1 vote190 views1 answer
Php absolute value
PHP