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 vote232 views1 answer
Take 10 skip 10 laravel
PHP
0 vote290 views1 answer
Codeigniter form open
PHP CodeIgniter
0 vote250 views1 answer
Query builder laravel getmedia undefined method
PHP
0 vote238 views1 answer
Laravel eloquent select one column in array
PHP
2 votes230 views2 answers
Laravel now date
PHP
0 vote246 views4 answers
Installing bootstrap ui in laravel app
PHP
1 vote237 views2 answers
Laravel return response view
PHP
2 votes279 views1 answer
Tl to usd
PHP
0 vote225 views3 answers
Symfony project directory
PHP
1 vote295 views1 answer
Wordpress get page slug
PHP Wordpress