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 vote177 views1 answer
While loop in laravel
PHP
1 vote160 views1 answer
Palindrome in php
PHP
0 vote252 views1 answer
Multi theme laravel
PHP Laravel
1 vote239 views4 answers
Dynamic base url codeigniter
PHP CodeIgniter
0 vote155 views1 answer
Laravel download file from storage with progress bar
PHP Laravel
3 votes192 views2 answers
Laravel Migrations from an existing database
PHP
13 votes195 views4 answers
Php get domain from url
PHP
2 votes185 views2 answers
<?php echo do_shortcode(' '); ?> with variable
PHP
3 votes210 views2 answers
Error handling in laravel
PHP Laravel
0 vote158 views1 answer
Appserviceprovider laravel share common settings for all controllers
PHP Laravel