I see some php53-* packages have come to iworx-unsupported. Any preliminary instructions on upgrading from the standard php packages iworx-unsupported supports? I’m not keen on running two versions of php 5.x (on staging or live). Since 5.2 is no longer supported, I’d like to move our php support to 5.3.
me to. need more informations from interworx.
We’ve used the procedure detailed here successfully:
Hope it helps,
I just finally moved to 5.2 from 5.1. I used the following YUM method, http://interworx.com/forums/showthread.php?t=3139
I think I’ll wait for an easy, officially unsupported yum update method comes along before going to go 5.3.
The procedure I pointed out above is a “Yum Method” and it is easy to do.
Quick question guys, whats the motivation (need) to move over to php 5.3? s it because you have scripts needing 5.3 or something else.
[QUOTE=CRServers;17971]The procedure I pointed out above is a “Yum Method” and it is easy to do.
Yes, it is, but it’s not under that “Officially Unsupported” space that makes me feel all warm and cozy inside
Although your method looks easy enough if anyone has a real need to upgrade, I don’t…yet.
Keep in mind guys that InterWorx has it’s own isolated sandboxed-in versions of PHP/Apache/MySQL which are used only for running the control panel and webmail. These are located with /usr/local/interworx and will not host or execute code located outside of the interworx install dir.
This means you can change the “system” PHP/Apache/MySQL (and by system I mean the instances that hosted sites run on) without breaking the panel. These are the php, php-* (with the exception of php-iworx but this doesn’t have a dependency on php), mysql-server, and httpd packages in yum. As long as the packages are compatible with the OS you are running and any existing client websites, you won’t break anything.
Some things to keep an eye out for:
- Updating PHP may break code on a client’s website
- Updating PHP to a version that isn’t packaged with an extension you need - make sure all the extensions you need are available from the repository you are updating from
- Updating MySQL and forgetting to run the mysql_upgrade script.
- Updating MySQL and not having old_passwords=1 in /etc/my.cnf which makes phpmyadmin unuseable from inside the panel.
- Updating apache and it not having a module you need.
- Installing a repo like DAG/rpmforge or atomic turtle and leaving it active. If you install these repositories:
yum update php php-[whatever packages you need]*
and then open the .repo file in /etc/yum.repos.d/ and set enabled=0.
otherwise you might find that rrdtool, spamassassin, clamav, etc. might get overwritten during an update. These packages (unlike php, httpd, and mysql-server) should not be overwritten by a 3rd party as they will become incompatible with InterWorx.
If you guys need more detail on anything let us know.