CentOS Web Stack

6 posts / 0 new
Last post
#1 Tue, 04/10/2007 - 17:56
BillDeLoatche

CentOS Web Stack

Do you support using the current CentOS Web Stack installation of PHP Mysql Postgresql Perl Httpd and Postfix or what do you recommend as far as these packages.

Tue, 04/10/2007 - 18:05
Joe
Joe's picture

Hey Bill,

I dunno. I've never heard of it.

We do recommend you use our Apache and PHP version 4 and 5, just because you need a particular setting in Apache's build (suexec-docroot) and all other PHP5 packages that I've seen for CentOS are stupid and have to replace PHP4. Our PHP 4 packages also add support for fcgi, which the default CentOS packages don't have.

But we don't really care what version of MySQL, Postfix, etc. you use, as long as their configuration files are in the usual locations.

--

Check out the forum guidelines!

Tue, 04/10/2007 - 18:35
BillDeLoatche

I am currently using Centos and Plesk on my production servers and was looking for a way to upgrade when I went to CentOSWebStack on the CentOS site at

http://wiki.centos.org/Repositories/CentOSPlus/CentOSWebStack

It was designed as an alternative for thoses needing php5 and mysql and such with a way to keep it updated with yum while waiting for CentOS5. But I have more faith in your recommendations since I haven't strayed from the standard CentOS repos because I don't want to break plesk, which they do enough of on their own.

I am also cuurently running a server with Centos 4.4 with postgrsql 8.0.8 and Mysql 4.1.20 and am using your 338 GPL on it but am interested in putting VirualminPro on it as soon as possible.

Any words of wisdom would be greatly appreciated as my licenses on 3 plesk servers run out in July.
A migration path would be great but I don't know if you have any plans for that.

Thanks Bill

Tue, 04/10/2007 - 18:55 (Reply to #3)
Joe
Joe's picture

Hey Bill,

<i>It was designed as an alternative for thoses needing php5 and mysql and such with a way to keep it updated with yum while waiting for CentOS5. But I have more faith in your recommendations since I haven't strayed from the standard CentOS repos because I don't want to break plesk, which they do enough of on their own.</i>

Ah, OK, sounds reasonable...but again, I'd stick with our PHP and Apache packages. Everything else you can go wild with. Because we're based on Webmin, nearly every version of everything that you could possibly want to use is already supported. We're not quite as restrictive as the Plesk and cPanel platforms in that regard. (We still manage to break stuff in our repositories quite a bit, but our QC is getting a lot better as time goes by and our processes for testing releases gets better. We also hear about problems fast now that we have several hundred users.)

<i>Any words of wisdom would be greatly appreciated as my licenses on 3 plesk servers run out in July.
A migration path would be great but I don't know if you have any plans for that.</i>

Sounds like you've already got a lot of wisdom there (moving from Plesk to Virtualmin!). But we'll be here to help. We don't currently do migrations from Plesk, but if you send us some backups we'll add it. So far, I don't think anyone has actually wanted Plesk migration badly enough to send us some example files (they can be &quot;dummy&quot; files that don't have valuable data or passwords), but it only takes a few days after we receive the backups for support to be added.

We already do Ensim and cPanel migrations, and it gets easier with each new migration type we add.

--

Check out the forum guidelines!

Wed, 05/23/2007 - 10:16 (Reply to #4)
michaeljc8

I want it! :)

I'll give you anything you want, even root access.

I want to go from Suse 9.2 and Plesk to CentOS and Virtualmin.

Let me know what I can do to help.

Michael

Thu, 04/12/2007 - 18:24
ADobkin

FYI, CentOS 5 is now final:

http://lists.centos.org/pipermail/centos-announce/2007-April/013660.html

I would think the CentOS Web Stack is now pretty much obselete (at least for the next couple of years), since CentOS 5 is a much better officially-supported option.

Topic locked