• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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