Originally posted by k-us
.......frage mich wirklich langsam wofür Plesk eigentlich konzipiert wurde, wenn es an den einfachen Webadmin-Dingen schon so scheitert...
I will answer in english so more people can understand.
Your question:
What's the main purpose of Plesk when even simple admin tasks fail?
I think the main purpose for Plesk is to keep away the "only one domain but server owners" from the config files in /etc/* and /var/lib/named/*. These people are happy with their system "as is". They have no need and don't need to customize their servers.
Plesk is a lot like Windows.
* Lot’s of colors but you are layers of encrypted scripts away from the hardware. If you change something in a config file, it will probably be overwritten by Plesk and you don’t get any notice that Plesk changed your congiguration.
* no more logging to /var/log/messages after update.
* Vendor lock in via binaries.
If there is a major bug/update you depend on the binaries SWsoft releases for your version of Plesk.(Try upgrading Spamassassin from 3.0.4 to current version of 3.1.1.)
* The documentation of Plesk is missing important parts:
1. Where to place configfiles for Apache that are actually read and included.
2. How to create domains in Plesk without creating zonefiles for DNS.
I think Plesk is for hobby users only and not for people that want to finetune their servers for their individual needs.
Just look at the subdomains. Each subdomain is located in a seperate directory tree. Why? Where can I change this behavior? I want to point my subdomain "product.company.com" and full domain "www.superproduct.com" to an existing webtree ../httddocs/superproduct/
These are some reasons I think Plesk is like Windows.
Lars