creatorbri
New member
- Joined
- Mar 3, 2011
- Messages
- 2
I'm new to DirectAdmin. I requested it be installed on my new VPS because I don't like some of the restrictions of cPanel, but there are some things that are a little frustrating, and I'm hoping that by explaining my situation, some of you can give me some pointers and advice that will help me make the most of this new tool.
See, I am the only person who will ever use my server. I don't need Reseller accounts or separate users; I am 100% responsible for everything. Naturally the idea of having to login as a user to be able to work with my domains is a little awkward, but it's tolerable.
My most pressing question:
I develop and run numerous web applications (mostly PHP-based) that each need their own VirtualHost record. Some of these apps involve multiple public document roots, served under various domains and subdomains, and none of them are called "public_html", but I can't seem to specify the directory path of the actual docroot.
How can I achieve this, and what other tips can y'all give me for operating a single-admin-user server with DA?
See, I am the only person who will ever use my server. I don't need Reseller accounts or separate users; I am 100% responsible for everything. Naturally the idea of having to login as a user to be able to work with my domains is a little awkward, but it's tolerable.
My most pressing question:
I develop and run numerous web applications (mostly PHP-based) that each need their own VirtualHost record. Some of these apps involve multiple public document roots, served under various domains and subdomains, and none of them are called "public_html", but I can't seem to specify the directory path of the actual docroot.
How can I achieve this, and what other tips can y'all give me for operating a single-admin-user server with DA?
