Hello Till, thanks for your reply!
ISPConfig has a standard, and this standard is that the name...
I have made myself misunderstood, sorry about that.
!!! I did not want to make ISPConfig down - quite the reverse - ispconfig is the best (free) hosting panel solution at all !!!
What I meant was that we do not impose standards to our
customers. In this case each customer can create their own folder trees without restrictions (inside the web root). But predefined folders are restrictions (my opinion). In some projects error
are used by our customers. I have to migrate more than 300 vhost from different server to a new multi-server-environment!
I´ll do this once[!], straight[!] and flawless! I think ispconfig could help me a lot!
In ispconfig and several other controlpanels, the standard name for thsi folder is web.
What makes the use of ispconfig attractive over other control panels? The same standards(?), same restrictions(?) or what?
Things like customized settings, stability, diversity... makes ispconfig attractive and it´s not necessary to compare it with other control panels - ispconfig "shows something a clean pair of heels" (I think this is like - etwas weit zurück/hinter sich lassen?).
Btw - advantages to define the paths in a common config (like /usr/local/ispconfig/server/lib/config.inc.php
) are clear code, simple to change, adjustment, debugg and customizable and not realy hard to do.
Thank you for your attention
just my 2 cent