Skipping Php Change In Compile

btaylor927

• July 30, 2015 12:10

We're trying to automate the roll out of new apache versions onto servers, but have the issue that some legacy systems are running PHP 5.2. Whilst we do plan to upgrade these in the near future, we still want to ensure they're on the latest apache builds. At the moment we're scripting the use of /scripts/easyapache --build to run through and put the latest apache builds in place, but what happens if this is run on a 5.2 server? Will it force the server up to 5.3 because of 5.2 not being included in the standard process or will it leave the PHP as is? If it's the latter, is there a simple way to have it skip the PHP part of the process and just rebuild apache? The docs aren't very clear on this.

• 

  sparek-3

  • July 30, 2015 18:32

  Not sure of the answer to your question. But this has always been something I didn't like about EasyApache. PHP shouldn't be tied to EasyApache. I would dare say nothing should be tied to EasyApache. EasyApache should be for compiling Apache. Want to install PHP? Have an EasyPHP script if you want to do that. Want to install ModSecurity? Have an EasyModSecurity script (or a DSO catalog that you can use, that's separate from EasyApache, to install Apache modules). This would clear up this issue for you. Updating Apache would just be a matter of running EasyApache to recompile Apache, without the worry that anything PHP related would break.

  0
• 

  cPanelMichael

  • August 07, 2015 19:02

  Hello :) You will not be able to continue using PHP 5.2 unless you install it as a custom module: .
  Thank you.

  0

Please sign in to leave a comment.