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 vote180 views1 answer
Phpexcel set row height
PHP
1 vote165 views1 answer
Php load specific post id on language
PHP
7 votes227 views2 answers
How to check the day of any date in php
PHP
1 vote202 views1 answer
Validation not exists with this id laravel
PHP
20 votes184 views3 answers
Make specific migration laravel
PHP
2 votes173 views2 answers
Empty table in laravel
PHP
0 vote191 views1 answer
Show woocommerce product variation in table php
PHP
9 votes204 views1 answer
A facade root has not been set phpunit
PHP
0 vote217 views1 answer
Divide page in pdf with page break using php
PHP
6 votes177 views6 answers
Laravel create project
PHP