We currently have the following info shown to admins in the website: But strictly seen, this is incorrect as the folder is the website's root and not the document root of the vhost. I wonder if we should change this and, if so, how. I guess we should either name it: Website Root: /var/www/clients/client0/web5 or we keep it as document root, but add /web to the path: Document Root: /var/www/clients/client0/web5/web So the options are: 1) Keep it as it is. 2) Rename the label to Website Root. 3) Keep the label but append /web to the path that is shown. Please let me know your opinions on this.
I'm in favor of option 2. Mainly because the mentioned quota is about that path and not only path/web Though I'm not entirely sure if renaming to Website Root is the way to go. As it would suggest to the common user it's still the same as Document Root. It needs a more explicit name.
The term/label Document Root is imho misleading, especially for persons who associate this term with the Apache Document Root directive. I tend to either rename it to Website Root as it was mentioned or append the web directory to the document root path. I personally prefer option 3, especially if https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6674 is implemented.
Another idea: hide the whole thing by default. This declutters the interface. I think this is not really used by clients anyway.
Only the admin can see it. And I guess I have to add something like this for https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6674 anyway soon.
I look it up here from time to time when I need the absolute path and not symbolic links. @till Why not move it to the top of the page and keep naming it simple, just Path or Folder. Can't get any clearer than that.
