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 vote108 views1 answer
Laravel login shows 404
PHP Laravel
6 votes88 views1 answer
Get domain from url cakephp
PHP
0 vote99 views2 answers
Laravel project make
PHP
0 vote108 views1 answer
Beautify var_dump
PHP
0 vote113 views1 answer
Get absolute path php file
PHP
-3 votes91 views8 answers
@foreac laravel
PHP
1 vote103 views3 answers
Base url dinamis codeigniter
PHP
4 votes122 views2 answers
Ubuntu laravel storage permission
PHP Laravel
1 vote115 views1 answer
Laravel queue work schedule cpanel
PHP Laravel
0 vote108 views1 answer
Wordpress use jquery in plugin
PHP