I'd like to see the ability to have multiple websites on one account without the need to set up a intro page to read the cgi.server_name.
If we had one main folder then the ability to add other folders and set up IIS to point to the different folders for different sites. Since the bandwidth and folder size restrictions would be based on the account it seems like it might be reasonable.
Thanks for the great forum!
-Ken

Unfortuneatly I don't think you'll be seeing this anytime soon.

You may want to look at our terms or service which addresses this issue:
http://hostmysite.com/termsofservice/

One good reason, is we would be forced to use host headers. IIS's performance really suffers once you get to a large number of sites using headers. Also most of our automation and business logic is geared around a single IIS site being connected to one hosting account.

But I do see your point. Athough a single index page with redirection is simple enough to do, perhaps we need a support section on how to do this in some different languages.

Thanks for the reply.
I'd be happy to whip a couple up in CF and .NET.
The only real downside as I see it is it's going to run on every single page request...
You make excellent points thoguh, and I hate to see IIS under any more strain.

This can also be done in apache with mod_rewrite rules. Its still not something we support officially, but if you have a reasonable request it may be something we can accomodate(e.g. I set someone up earlier this week with boards.mydomain.com to go to his website's forum).

Again, the goal is to avoid strain on the server from customers hosting dozens of websites under one account.

You lost me when you said the "a" word. (apache)
My requests are hardly ever reasonable but I appreciate the answer.

Apache is the web server running on our Linux servers, so if you don't have any Linux sites then this doesn't really apply to you.

heh-heh thanks, I know what apache is I just have never worked with it so it's inner working are a dark mystery to me.
I hope they can remain that way.

Ken,

Im an MS man myself, and am now working with apache on suse 9.1... and it's STILL a mystery to me... *sigh*

Here's a script to move requests to one url to an internal directory to "mask" a url.
In the application page.


If it finds the url to be cavypop.com it just adds the cavypop directory (which is in the root folder) to the page request.
This is how I run hamsterific.com and cavypop.com on the same account. There is a cavypop folder containing it's pages in the hamsterific sites directory.
You could host as many sites as you wanted this way as long as you didn't exceed your hosting plan's specs.

I can not get this to work for the life of me. For Example..(using the above as an example) It works fine with files you link to in the cavypop directory. But once you go deeper inside cavypop, it won't work. I do a lot of advanced coldfusion development but this one is stumping me..I think I'm overlooking something..

I've tried using abolute and relative links. I would try creating a mapping, but the CP doesn't let you do it on linux hosting. I hate linux but only have it for PHP and ColdFusion together.

Can someone shed some light?

For reference..my directory structure..
+ROOT DIRECTORY
+folder1
- Application.cfm
-subfiles domain 1
+folder2
- Application.cfm
-subfiles domain 2
+ Application.cfm