I had today the third time in this month an unpleasant conversation with agencies, the agencies say they can no longer order from us the hostings for their customers because they use CMS systems or frameworks which needs the DocumentRoot on /public.
The customers also say that we adjust the DocumentRoot within 15 minutes after they have sent us a ticket but that this is impractical because they have to wait and now and then it happens that work is done at night and we can only adjust the docroot on the next day and the customer have to wait to.
Also DocumentRoot switching allows staging which is also a big plus.
We’ve migrated one customer back to cpanel, there the option exists. But I want to get away from it and not back but I don't see a chance here to not lose customers because of a trivial path / DocumentRoot "problem". Discussions like: put the stuff in the home and make the public_html the /public are rejected with the argument, that this goes otherwise with every hoster... Also, the agencies say that this does not work because they deploed the code via git from their development system, also with composer there are some problems.
I can fully understand. What I can not understand is, why I can change the docroot in DA for subdomain but not for the main domain (as enduser)?
Via CMD_CUSTOM_HTTPD (as admin) this is all very easy, is there a possibility that you can do this via a plugin?
DA seems to fully support modified docroots, as evidenced by this page: https://docs.directadmin.com/directadmin/general-usage/directadmin-binary.html#show-documentroots why can't the end user not set itvia GUI?
Anyway, I’ve created a feature request for this: https://feedback.directadmin.com/b/feature-requests/documentroot-modification-for-the-maindomain
Please vote for it!
Thanks
The customers also say that we adjust the DocumentRoot within 15 minutes after they have sent us a ticket but that this is impractical because they have to wait and now and then it happens that work is done at night and we can only adjust the docroot on the next day and the customer have to wait to.
Also DocumentRoot switching allows staging which is also a big plus.
We’ve migrated one customer back to cpanel, there the option exists. But I want to get away from it and not back but I don't see a chance here to not lose customers because of a trivial path / DocumentRoot "problem". Discussions like: put the stuff in the home and make the public_html the /public are rejected with the argument, that this goes otherwise with every hoster... Also, the agencies say that this does not work because they deploed the code via git from their development system, also with composer there are some problems.
I can fully understand. What I can not understand is, why I can change the docroot in DA for subdomain but not for the main domain (as enduser)?
Via CMD_CUSTOM_HTTPD (as admin) this is all very easy, is there a possibility that you can do this via a plugin?
DA seems to fully support modified docroots, as evidenced by this page: https://docs.directadmin.com/directadmin/general-usage/directadmin-binary.html#show-documentroots why can't the end user not set itvia GUI?
Anyway, I’ve created a feature request for this: https://feedback.directadmin.com/b/feature-requests/documentroot-modification-for-the-maindomain
Please vote for it!
Thanks