Skip to main content

EasyApache simple compile

Comments

5 comments

  • cPanelMichael
    Hello :) Could you elaborate on the specific method you have used to add/configure custom modules? Thank you.
    0
  • sparek-3
    We have a lot of custom patches that we apply to suPHP that we compile. I compile mod_deflate as a DSO module and include it on the Apache Configuration. The same for CloudFlare. I also compile mod_security separately. Actually if you just had a step by step of what and which patches you apply to the Apache source before compiling, and the compiling parameters used, I could just compile it manually. That would actually be preferable to me.
    0
  • cPanelMichael
    To elaborate on my previous post, I am curious if you simply manually make those changes from the command line, or if you utilize script hooks to automatically make those changes during the EasyApache build? If you don't use script hooks, you may find them useful for what you are doing: EasyApache - Script Hooks Thank you.
    0
  • sparek-3
    No, I don't use script hooks for this. A lot of the stuff I do predates when cPanel pulled EasyApache together to do all of this. I've always been kind of mind boggled as to why Apache and PHP are smashed together into one EasyApache. It looks to me like EasyApache should be for Apache. And if you want an EasyPHP you can make an EasyPHP. I don't use EasyApache to maintain my PHP on the server. I wrote my own system for doing this a long time ago. It allows me to include features with a simple configure command line hook on PHP installs. It also allows me to update PHP as soon as a new version of PHP is released, instead of having to wait for it to go through cPanel's EasyApache QA. It would almost seem to me that EasyApache would be better served if it was replaced with a simple script or set of instructions, i.e:
    wget http://download.nextag.com/apache/httpd/httpd-2.2.29.tar.gz tar -zxf httpd-2.2.29.tar.gz cd httpd-2.2.29 ./configure ... make make install
    Add steps as necessary for what cPanel considers a "common" Apache compile (I believe there are certain patches that are installed, although I'm not sure of what order). And if certain server admins want to wade into the water of customizing, they can do so. Once you get set on an Apache (or PHP for that matter) configuration, I really don't see why it should be recompiled that often. The only times I see it necessary to recompile is when a new version is released. And by making the steps much more transparent, you wouldn't have to run it through QA. The same could be said of Exim, Dovecot, PureFTP, MySQL, etc. I can understand cPanel providing a recommended install, but these services really should be installed at the discretion of the server admin. I'm not saying that the EasyApache system is a bad thing, I just wish there were more transparency so that server admins that want more control over how services are set up, can do so.
    0
  • JacobPerkins
    Hi! At this point, we're trying not to make many more changes to EasyApache 3. We're full hands on deck on our EasyApache 4 project, which will allow this type of customization you like! If you haven't had a chance, please take a look at our post here and provide feedback on how we can make this process a lot easier for you!
    0

Please sign in to leave a comment.