There is practical reason to allow users to manage their sites DOCUMENT_ROOT, they call it "Laravel".
Every 5-th support request in our helpdesk is "How can I change document_root from public_html to public_html/public." There is a two ugly solutions is a) .htaccess b) symlinking. So there is a production necessity to give possibility to users to change theirs document_root.
You have to see it from a service provider's point of view. Everything can be configured via the web server configuration, that is not the point. The point is, that it is not particularly advantageous that working time has to be spent on basic things. And this is one of the most common requests from clients.
For admins:
The third solutions is: change it in the httpd-config
The forth solution: use the virtual templates for your httpd config
Fifth: give your users a domain-variable and use that in your virtual template
"The point is, that it is not particularly advantageous that working time has to be spent on basic things"
I don't think these are basic things. In cPanel or Plesk you cannot even do these things.... if I remember correctly. For because of the (unflexible) path-structure in those platforms, I ran back to directadmin ;-)
Activity Newest / Oldest
Roman Mazur
Plus! There is already a possibility to change docroot for subdomains and I see no reasons not to give this feature for domains itself.
flexjoly
downvote > nice-to-have
Not needed, can be done by httpd-config etc
Directadmin is The BEST in handling document-root compared to cPanel and Plesk.
Roman Mazur
Hi!
What do you mean by that?
There is practical reason to allow users to manage their sites DOCUMENT_ROOT, they call it "Laravel".
Every 5-th support request in our helpdesk is "How can I change document_root from public_html to public_html/public." There is a two ugly solutions is a) .htaccess b) symlinking. So there is a production necessity to give possibility to users to change theirs document_root.
Dominik Bauer
You have to see it from a service provider's point of view. Everything can be configured via the web server configuration, that is not the point. The point is, that it is not particularly advantageous that working time has to be spent on basic things. And this is one of the most common requests from clients.
flexjoly
So maybe we need a better faq.
For admins:
The third solutions is: change it in the httpd-config
The forth solution: use the virtual templates for your httpd config
Fifth: give your users a domain-variable and use that in your virtual template
"The point is, that it is not particularly advantageous that working time has to be spent on basic things"
I don't think these are basic things. In cPanel or Plesk you cannot even do these things.... if I remember correctly. For because of the (unflexible) path-structure in those platforms, I ran back to directadmin ;-)
Roman Mazur
> Fifth: give your users a domain-variable and use that in your virtual template
It's exactly what we need. Every domain have a bunch of predefined vars which used in virtual_host*.conf & nginx_*.conf
There is already a DOCROOT variable in templates
|?DOCROOT=`HOME`/domains/`DOMAIN`/public_html|
and all the DA devs team left to do is just make it browsable & editable via API/GUI.