How do I update PHP and run multiple versions?

Submitted by bob7123 on Thu, 11/19/2009 - 15:04

Hi there,

I just upgraded to Virtualmin Professional. I did this in large part because of a) the application library, and b) because the PHP section of the feature comparison chart says:

"PHP 4 and PHP 5, switchable per-domain and per-directory, with suexec and mod_fcgid"

Well, once the professional upgrade was installed, I first tried to fire up the roundcube script, which promptly failed, telling me I need PHP 5.2. (I have PHP 5.1 installed)

SO, how do I a) upgrade to PHP 5.2 and b) take advantage of the ability to run multiple versions of PHP as advertised above?

Also, if I run multiple versions of PHP, am I limited to just one 4.x and one 5.x version, or can I have more? (all that said, unless I have a definite need for an older version down the road, using the latest stable PHP should be fine)

THANKS!!!

-Bob

Status: 
Active

Comments

Submitted by bob7123 on Thu, 11/19/2009 - 15:35

Sorry, I should have mentioned I am on a brand new Centos 5 box.

Submitted by JamieCameron on Thu, 11/19/2009 - 16:54

When you initially installed virtualmin, was this using our install script?

Submitted by bob7123 on Fri, 11/20/2009 - 05:15

Hi Jamie,

Yes I did, on a freshly installed Centos distribution (I did a yum update first to get everything current)

Then after using the GPL version for only several hours (and creating 1 virtual site) I upgraded to pro.

Submitted by bob7123 on Sat, 11/21/2009 - 05:13

Thanks Jamie, that helps a lot.

I have a few other start up questions...

I am migrating away from a Cpanel system. I have several domains which have their own spamassassin user_prefs file which users can use to put their own rules. Is this possible with Virtualmin to do this? If so, where would I place these files and/or access them in the UI?

If not, is there a fallback where I can access a server wide user_prefs file?

Also Cpanel uses exim for mail delivery, and is set up to process mail filters for each domain on the box.

I realize Virtualmin uses postfix, and I'll figure out how to do the translation to the new syntax, but where would I place the filters on my new box? And again, is it possible to have files on a per domain basis or just server wide?

Thanks again for your help!

-Bob

Submitted by JamieCameron on Sat, 11/21/2009 - 15:30

Yes, you can have per-domain and global spamassassin configs - they can be set by selecting a domain from the left menu, then going to Services -> SpamAssassin.

As for procmail mail filters, they can be global or per-user .. there isn't really any official way to set them up on a per-domain basis.

Submitted by bob7123 on Tue, 12/01/2009 - 07:56

Hello again.

I seem to be settling into using Virtualmin nicely, but I still have a few startup questions..

-In the procmail filters you mentioned above, where are they at the domain level, both in the UI and in the file tree? If they are not available on a domain basis, where would the per user filters be (in the UI and/or file tree)

-Similarly, at the domain level, where in the file tree are the spamassassin filters?

-How do I set the default address to some kind of null value so unknown user's mail for a domain is dropped? (no reply)

-How can I change the favicon.ico that the main Virtualmin site uses? (I am using the default theme, if that matters)

Thanks! -Bob

Submitted by JamieCameron on Tue, 12/01/2009 - 13:40

1) The domain-level procmail filters are not in the UI, as they are generally maintained by Virtualmin based on your spam filtering settings. However, the files can be found under /etc/webmin/virtual-server/procmail . Per-user filters are available in Usermin (on port 20000), via the Filter Mail link on the left menu. This corresponds to the users' .procmailrc files.

2) Per-domain spam filters are at Services -> SpamAssassin, and under /etc/webmin/virtual-server/spam

3) You can create a catchall address that drops email via the Edit Mail Aliases link on the left menu.

4) There's no way to change the icon, sorry .. apart from editing the file at /usr/libexec/webmin/virtual-server-theme/favicon.ico , which would be over-written in the next upgrade.