Installing modified source code in EasyApache4

cgibinux

• September 01, 2018 00:03

I'm wondering if the info in the pages above are relevant in easyapache4 if RPM's or SRPM's are used. But instead of PHP it's with proprietary additions to apache's deepest core (not a module) source code. If not, what is the new equivalent method for EA4. I never made an RPM before. Haven't switched to EA4 yet. Operating system: CentOS 6.10

• 

  cPanelLauren

  • September 03, 2018 17:50

  Hi @cgibinux EA4 is an entirely different system than EA3. We do have a tutorial on how to build custom packages for EA4 here: Thanks!

  0
• 

  cgibinux

  • June 26, 2019 04:52

  Followup to I have used osc to build custom easyapache4 rpms but I don't see any instructions on the proper way to install them so a cpanel update would always use the custom apache RPMs and use the cpanel RPMs of everything else. Things to consider: My custom osc project just contains one subproject ea-apache2 I installed osc and did things on a raspberry pi, not the server it'd install on. The RPMs were made by openSUSE. I'm guessing it'd involve adding an RPM or yum repository that points to the openSUSE subproject, or maybe installing osc on the server and doing something.

  0
• 

  cPanelMichael

  • June 28, 2019 18:26

  Hello @cgibinux, The following quote from the resource linked earlier includes examples of how this works for Apache modules and PHP modules: [QUOTE]Official cPanel Sources: cPanel Production RPM Sources This is cPanels upstream Production "branch" of RPMs that are live on customer systems. Contributions Apache Modules: ea-apache24-mod_xsendfile - mod_xsendfile Apache module for EA4. ea-php##-php-htscanner-enhanced - Experimental htscanner-enhanced packages.
  If I understand correctly, you are not building a custom EA4 RPM for a new Apache or PHP module, but rather you want to replace the existing ea-apache24-2.4.39-4.4.1.cpanel.x86_64 RPM with your own custom RPM. Is that correct? If so, can you provide more information about the steps you have taken thus far? Thank you.

  0
• 

  cgibinux

  • June 29, 2019 04:54

  Hello @cgibinux, The following quote from the resource linked earlier includes examples of how this works for Apache modules and PHP modules: If I understand correctly, you are not building a custom EA4 RPM for a new Apache or PHP module, but rather you want to replace the existing ea-apache24-2.4.39-4.4.1.cpanel.x86_64 RPM with your own custom RPM. Is that correct? If so, can you provide more information about the steps you have taken thus far? Thank you.

  
  Correct, on a raspberry pi, I used osc to branch from just isv:cpanel:EA4 ea-apache2, checked out the files, created a custom patch to apache, did a commit. On the build.opensuse.org site it shows that it compiled successfully May 30th for CentOS 6 & 7 with a long list of apache rpm files. ea-apache24-2.4.39-4.8.1.x86_64.rpm (2.36 MB) and many rpm's of modules, that's a different version than the ea-apache24-2.4.39-4.4.1.cpanel.x86_64 installed on the centos 6 server. The directions were to a "production" repository/branch, should I should have done another one to be at the exact same version? I haven't tried using them on the centos 6 server. Looking for the next step. In case the custom RPM's don't work, it would be helpful to have instructions on how to quickly revert back to the cpanel version of apache.

  0
• 

  cPanelMichael

  • July 03, 2019 19:32

  Hello @cgibinux, The instructions we provide on and we can obtain feedback from Development to determine if a different approach is recommended.

  In case the custom RPM's don't work, it would be helpful to have instructions on how to quickly revert back to the cpanel version of apache.

  
  The "yum downgrade" command is useful in some cases, however you must also know which dependencies you must also downgrade. It's helpful to setup a development server for testing custom RPMs before pushing them to production. For information on how to obtain a Developer License, see the link below:

  0

Please sign in to leave a comment.