Security updates install themselves every day on a provisioned server, without rebooting it. Everything else waits for you: XenoPanel checks a server only when you ask, and never in the background.
See what’s out of date
$ xenopanel server update web-1 # reads the server; changes nothingThe report lists:
- packages with updates, with security updates marked, and whether the server needs a reboot
- a newer MySQL patch, when this XenoPanel release has one
- newer PHP patches for each site, in the series it’s on
- Cloudflare’s address ranges, when they’ve changed
- files XenoPanel wrote that were changed by hand since
Apply what you choose
$ xenopanel server update web-1 --security-only
$ xenopanel server update web-1 --apt # every package update
$ xenopanel server update web-1 --mysql
$ xenopanel server update web-1 --cloudflare
$ xenopanel server update web-1 --all # --apt, --mysql and --cloudflare- Packages: config files you or XenoPanel changed stay as they are. Afterwards XenoPanel says whether a reboot is needed and for which packages. It never reboots a server itself, so you choose when.
- MySQL: XenoPanel dumps every database first, then moves MySQL to the new patch. The previous patch stays installed, so a failed step goes back to it.
- PHP: a newer patch is never applied to a site on its own. The report shows the command for each site, for example
xenopanel site php example.com --patch 8.4.28, so you can move one site and check it before the next.
Files changed by hand
XenoPanel remembers each file it writes. When one was changed by hand, the report shows the difference, and you decide:
$ xenopanel server update web-1 --keep /etc/nginx/sites-available/example.com.conf
$ xenopanel server update web-1 --restore /etc/nginx/sites-available/example.com.conf--keepkeeps your version. From then on it isn’t reported, and no XenoPanel change overwrites it.--restoreputs XenoPanel’s version back.
A site’s overrides.ini is yours to edit, so it’s never reported.