• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Upgrading OS Components: Building from Sources & Keeping Plesk in the Loop

F

fatbear

Guest
I'm just getting started with Plesk and would like to be able to upgrade my system components (Apache, MySQL, PHP, named, mcrypt, gd, and other libraries). However, I do not wish to use rpms to do so. I compile from sources (sometimes with custom modifications) and then install. I am not interested in using the yum tool that I've seen posts about.

I don't know how Plesk knows where to look for installed components and don't want to break it. The documentation for Plesk (that I've found) doesn't address what I would consider to be basic stuff: how does Plesk know about and manage OS components?

Thanks for any assistance!

Enjoy,
Steve Amerige
Fat Bear
 
Back
Top