• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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