updating the version of php in apache2triad

[beeswax]

Moodle 1.9.1 is generating some errors and it seems that the version of php I'm using needs updating. I've checked out the A2T forums but i can't find anything which makes sense to a non coder. Does anyone have a guide, or can point me to a guide which will hold my hand through this change?

[edit] can anyone recommend a program that performs the same functions as Apache2Triad, but which updates automatically? It needs to be able to handle a lot of users (1200+) and to run on windows?

[kmount]

WampServer seems pretty good especially given it offers "Addons" as different versions of PHP/MySQL etc.

It seems to be a lot more maintained than apache2triad.

Install PHP 5 Apache MySQL on Windows : WampServer

[beeswax]

I've just installed this on my laptop to test the Edugeek Joomla (1.5) package, but haven't had too much time to go too deeply into it. there are a lot of users it has to handle though.

[kmount]

I would imagine the spec of the server is more of an issue than the software to be honest.

[FN-GM]

@beeswax, I have run into the same problem but overlooked it until now. We will be running a separate server for our VLE and it will most probably be Linux. It always seems easier to sort out Linux webservers.

We are keeping apache2triad for our main website though, it’s a shame they have stopped developing it.

[beeswax]

I don't think we'll be going down the Linux route here Zak. I tried about 18 months/2 years ago but it didn't meet with too much enthusiasm.

[kmount]

So what spec is the server...

[beeswax]

HP Proliant ML350 G5, dual core 1.86 Xeon, 2Gb of memory. 1.5Tb storage. We're also running the school website off it.

[kmount]

Depends upon how many concurrent users you're looking at holding, but to take around 250 concurrent, I reckon you'd need more oomph there.

Link to the Moodle Requirements

[beeswax]

Thanks for the time and effort

[Jona]

I think it's generally a bad idea to allow apache and php to auto_update themselves as occasionally you get a bad build or a build that breaks which would bring you entire site down, your better off scheduling a maintenance period and doing a manual upgrade.

I would always recommend that for production sites people get the original apache binary and install php, et all manually.

I would have thought it wouldn't be too hard to update php you might get away with just copying the new php files over the old ones, try it on a test machine first.....