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

1 vote354 views1 answer
Foreach stdclass object php
PHP
0 vote339 views1 answer
Call to undefined method Illuminate\Session\Store::set()
PHP
10 votes290 views4 answers
Unset php
PHP
0 vote352 views1 answer
Laravel unknown column updated at
PHP Laravel
1 vote315 views1 answer
Causes of class not found in laravel
PHP
5 votes304 views1 answer
Push key value array php
PHP
0 vote331 views1 answer
Publish laravel scout
PHP Laravel
0 vote337 views1 answer
Laravel collection times
PHP Laravel
0 vote311 views1 answer
Php inline if condition date time
PHP
0 vote309 views1 answer
Auto complete order
PHP