apache conf, is this possible via a ensim

hdotnet · 30th October 2007, 10:07 AM

I'm looking for some reseller/shared hosting for a client.

The current sites are made up of a number of related domains that
all utilise the same docroot so as to be managed by the same CMS.

The situation is best described by a bit of apache conf...

<VirtualHost *:80>
ServerAlias www.domain1.com,www.domain2.com,www.domain3.com
ServerName www.domain.com
DocumentRoot /path/to/docroot
</VirtualHost>

The effect of the above obviously being each domain serves from the
same vhost and codebase for the CMS.

Is this possible via ensim?

At present this is botched via the add-on domains feature within cpanel, and a heap of redirects/symbolic links.

UH-Matt · 30th October 2007, 10:29 AM

No this is not possible on our hosting, as each site has its own chroot jail with its own complete filesystem, completely restricted from any other site for security purposes. There is no flexibility in this either.

hdotnet · 30th October 2007, 10:32 AM

is that because an ensim account can't add on domains?

sorry... ensim noob

MrBen · 30th October 2007, 11:01 AM

You can alias multiple domains to the same site but they will then share all the other services like stats, email, ftp etc. You can't edit the apache.conf directly yourself though.

Ben

hdotnet · 30th October 2007, 11:20 AM

Quote:

You can alias multiple domains to the same site but they will then share all the other services like stats, email, ftp etc. You can't edit the apache.conf directly yourself though.

Sharing stats and the like is not a problem. A seperate MTA will more than likely be used too.

So does aliasing (in ensim) mean that using domain1.com stays at domain1.com or will it forward to domain.com?

hope that makes sense

UH-Matt · 30th October 2007, 11:25 AM

Using domain1.com will stay as domain1.com it has its own virtual host container, just the same document root as the master domain.

hdotnet · 30th October 2007, 11:35 AM

Matt... a bit like this then?

Quote:

<VirtualHost *:80>
ServerName www.domain.com
DocumentRoot /path/to/docroot
</VirtualHost>

Quote:

<VirtualHost *:80>
ServerName Welcome to DOMAIN2.COM
DocumentRoot /path/to/docroot
</VirtualHost>

ie 2 vhosts, diff domains, same docroot. Your first reply to my post wasn't too promising!

apologies, just seeing if this is worth the effort.

I understand UH have a 30 day guarantee. Is it possible to sign up and to either:

1) edit my own PC's hosts file ...
2) point some A records for each domain ...

...so I can test out the ensim webserver configuration with this client's setup?

basically I want to test it out as much as possible before actually changing the name servers.

Being on a UK server is an absolute must for this client.

UH-Matt · 31st October 2007, 12:26 AM

Im not aware of any 30 day guarantee. If you signup you can signup on a monthly term and at worst lose your 1st month if it doesnt work out for you. We dont offer money back, no.

Yes you could edit your PC's hosts file and try it out properly to see if things work out for your system, and yes our vhosts look like the example you posted.

Simon · 31st October 2007, 07:31 AM

From the apache conf you posted, it looks like you just need a couple of domains aliased to one account, that is easily done, this does however mean that everything about these domains will be aliased mail, web, ftp, ....
For example if you have bill@domain.com, then you will also have bill@domain2.com, and all emails will be collectable from a single pop box, instead of 2 different ones.

Aliasing doesn't automatically mean that the aliases will be forwarded to the main domain but that could be done with a simple htaccess rule but I don't think thats what you want.

depends how much these sites share, but it sounds like it could be possible, how do you normally work the email addresses? are they independant, or would it be ok to share the pop3 mailboxes?

hdotnet · 31st October 2007, 01:13 PM

Simon...

I understand your point re aliasing of domains, however the client is going to take the plunge with google apps for their email so its not really an issue.

Matt...

Re 30 day guarantee. I could swallow the cost of a month, as long as I was sure that everything was done between UH and myself to get it going.

On the reseller page there is nothing about shell access... Is this allowed / restricted? If it is restricted is there a page/info about them?

Thanks for the info guys, much appreciated.

Alex. · 31st October 2007, 04:52 PM

Shell access is allowed via SSH (look on the package features page)

Vger · 1st November 2007, 03:31 AM

Quote:

however the client is going to take the plunge with google apps for their email

If this is the same as Google Mail for Business and you're using Dynamic PHP Based sites then you'll find it's not suitable.

Vger

MrBen · 1st November 2007, 08:31 AM

Why? All you do is point the MX records at Google?

Ben

hdotnet · 1st November 2007, 02:18 PM

@Vger

Email and web are 2 separate things. What does a dynamic php site have to do with email?

All you do is change the MX record in your domain and you're good to go.

IMHO its often a good idea to not put all your eggs in one basket when it comes to a host, especially a cheap one (not that UH can't handle it I'm sure).

Migrating mailboxes between hosts can be one of the most difficult things to do with finding a host... If you can outsource that part of the operation to a reliable email provider then everything becomes a lot easier, and the gmail offering is hard to resist feature and space wise, especially long term.

I'm sure UH wouldn't mind not having to handle another domain and all its spam anyway ;-)

hdotnet · 1st November 2007, 04:39 PM

k. tx for help everyone.

I signed up for a reseller account, setup the aliases, transferred the files and db, and bobs your uncle... the sites work.

dead easy so far, although I have yet to change nameservers!

Note to UH-Matt:
Biggest beef I had with the whole process was finding my error_log and access_log's so they could be tailed for info. I eventually found the path info in the control panel, but perhaps you should stick an article in the knowledge base.

Also, is there a list of allowed ssh commands anywhere?