Re: control panel
> * It requires you to do mostly everything via its (limited) web
> interface. There are overrides files of some kind, but they do not
> always work.
This is one aspect where the expensive Cpanel does do quite well... they
have tons of scripts which you can MANUALLY execute to get certain things
going. It is also not too hard to understand what it is trying to do most
of the time, whereas with Plesk it is harder to figure out.
Of course, if you are a novice and/or simply stick with the stock Plesk
web interface and stuff, you would be fine, but for those that need to
customize things its quite a nightmare.
And be very... VERY careful about upgrading Plesk. If something goes
wrong, the only advise they give you is to restore from backup and try
again... never mind downtime or anything. AND if you do end up getting
them to help, their response is usually unhelpful.
They have improved in recent times though with support not taking a week
to reply, but still... be careful.
> * Rather than using a system-wide configuration file with all common
> parameters, it writes all common configuration parameters to all
> vhosts configuration files, thus effectively blocking you from
> overriding them on a per-vhost basis, even if many of those
> configuration parameters do not always make sense.
> * If you nuke one of the per-vhost configuration files and recreate them
> sensibly (or even slightly modify one of them), it fails over and dies
> in all sorts of horrible ways.
Yes, the way they configure things is to have the main httpd.conf include
various separate vhost files, and the vhost files actually contain the
configuration information for each site. Some people like it this way,
some prefer httpd.conf to have everything.
> Its web interface indeed looks quite good provided you have a graphical
> browser, but that's about it. Oh, and it only runs on RedHat.
Cpanel also only works on RedHat and a number of others... Debian still
doesn't work properly. Its been in "BETA" for about 2 years now.
Reply to: