HestiaCP and distro updates. Is this right way to handle updates?

Hi,

Currently I am running latest HestiaCP version on Debian 12 + have separate staging server there I perform all updates/upgrades/tests before applying them on prod. I am not talking about major verion upgrades for example from Debian 11 to Debian 12. Just regular distro updates.

However I started questioning if this correct/right away to do it. Currently I do two things:

  1. I enable automatic security updates (unattended-upgrades)
  2. I run weekly (manually) this command sudo apt update && sudo apt upgrade -y && sudo apt-get autoremove -y && sudo apt-get remove --purge -y software-properties-common

The second command raised my eyebrows because it did update PHP and some other components that HestiaCP manages. Unfortunately I forgot to save the final output. So, I started to wonder if this is correct way to go?

I have somehow limited knowledge, but have successfully managed one Ubuntu server for +5 years and updates, but it did not have any control panels. Just some node.js apps and static websites. This was basically all I did to keep server up-to-date and secure, but perhaps I should take different approach with HestiaCP?

Suggestions and recommendations are welcome :slight_smile:

apt update && apt upgrade should be enough to update php…

I mean I was more worried if it will conflict somehow with HestiaCP updates, since you pack it together with HestiaCP already.

For website we use the php in Ubuntu repo. For the pannel we ship a other package called hestia-php

3 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.