#!/bin/sh if [ $contents -gt 0 ]; then rm -rf /home/$username/domains/$domain/subdomains/$subdomain fi exit 0;
Last sub is a subdomain name, for example if you had ditto.mydomain.com, the full path to it would be /home/username/domains/mydomain.com/subdomains/ditto. Also, I forgot to add a removal script. The following needs to be added to /usr/local/directadmin/scripts/custom/subdomain_destroy_post.sh:
#!/bin/sh rm -rf /home/$username/domains/$domain/subdomains/$subdomain exit 0;
This feature request has been in the versions system for quite some time.
However, it's not an easy fix as much of the way the templates are setup will break if we change variable structures for anyone who are using custom templates or the custom httpd config tool.
It might not be impossible, but if it's implemented, a completely backwards compatible setup would be required, which could be tricky.
Since my created Feature Request thread was locked, I will post my message here, since this is the only other Feature Request thread on this topic.
I am absolutelly shocked, that DirectAdmin still has not implemented "Document Root" feature. This should be listed as a priority.
Please consider this feature (https://www.directadmin.com/features.php?id=1007) as a priority.
What do other DirectAdmin users think about this?
Never needed it, because it's very easy to create a subdomain as user and also use it like that subdomain.What do other DirectAdmin users think about this?
Never needed it, because it's very easy to create a subdomain as user and also use it like that subdomain.
The subdirectory made for the subdomain IS the subdomains root directory so that's easy to use and most directadmin customers do know this.
Probably the reason this is not a number 1 priority.
There are some special cases in which people want to have http://sub.domain.com not pointing to http://www.domein.com/sub for some reasons but we never needed this. It might be necessary in some cases I heard from former cPanel admins.
So I don't mind if it would be implemented, but I also don't mind if it doesn't.
Yes it does and you have all the funciotnality as if it was a domain (meaning email @subdomain.domain.tld, subdomains as sub.subdomain.domain.tld etc)
Having the domain root in /home/account_username makes things confused, having a domains subdirectory where all the user's domain are stored it's way more clean, specially if a user have multiple domains.
I do agree and I would like to have something like /home/account/domains/domain.tld/subdomains/subdomain/private_html
But I do also understand that changing this "standard" configuration after all those years and with many customizations done on the template (I for example have tons of custom templates) will require quite a bit of work for DA and for everyone who does customize his templates.
Said that, I wouldn't mind have to rework the template if the goal have dedicated subdomains folder and I believe we will gonna get there at some point