[BlueOnyx:00136] Re: PHP Question

[Michael Stauber]

Hi Michael,

> If I could make a humble suggestion, since you have forked BQ into BlueOnyx
> maybe it's time to think about rolling the PHP the admin webserver needs
> into a separate RPM and location so that the default webserver might be
> more easily upgraded and changed without risking the system.

Yeah, this was contemplated long and hard prior to release. Especially at 
times when we were really fighting with the odds and sods which stood in the 
way of Sausalito running under PHP5. Which it flatly refused for quite some 
time, until we finally tackled that obstacle.

At that time the idea was to keep PHP4 for the GUI and simply just "move" it 
out of the way of the vendor supplied PHP-5.1.6.

Likewise, with PHP-5.1.6 being a bit aged (but the CentOS guys keep it patched 
security wise) the next idea was just what you suggested: Keep the GUI using 
PHP-5.1.6 and provide an additional and more modern PHP for Apache. 

However, the issue here is: PHP upgrades often enough. Or there are things 
that need to be patched security wise. If we step away from the CentOS 
supplied PHP, then updates must be provided for it as well. Going that extra 
mile - and doing it free of charge - doesn't sounds really compelling. :o)

Upgraded PHP PKGs (PHP-5.2.8 at the moment) are can be ordered through 
Solarspeed for those that need it. It costs a few bucks (50,- EUR) , but once 
you have it, future updates will cost only a fraction of what you paid 
initially (25,- EUR per update).

> But at this point it seems like it could enable better security and easier
> upgrades by allowing the CentOS PHP packages as they are released.

Exactly. The CentOS provided PHP-5.1.6 will be kept updated through YUM and 
unless you really need some PHP-5.2.X functions it's the best choice in the 
longer run.

-- 
With best regards

Michael Stauber