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 vote147 views1 answer
Laravel echo server
PHP Laravel
1 vote140 views2 answers
Running laravel as host
PHP Laravel
0 vote138 views1 answer
Slow laravel testing
PHP
5 votes153 views2 answers
Laravel 5 use env variable in blade
PHP Laravel
-4 votes119 views1 answer
Alert laravel 7
PHP
1 vote150 views3 answers
Wp site url link from admin
PHP Wordpress
2 votes127 views3 answers
Laravel get file contents from storage
PHP
0 vote164 views1 answer
Referencing constant in config laravel
PHP
0 vote99 views1 answer
Laravel auth trying to get property 'instid' of non-object
PHP Laravel
0 vote148 views1 answer
Insert value in session in laravel
PHP Laravel