> Be careful of wildcard settings on your sites. > Yeah it's cool but Search Engines do not like it at all.
The search engines wouldn't matter since the domain would only be for the CMS site. That's non-public anyway. The scenario you describe is a bit more complicated than what I was considering. When I say that I would be building "custom websites", I essentially mean that I would handle not only the site design and development for the client, but I would also register their domain, if they needed one, and handle the DNS manually. I wouldn't know how to begin to build a site that automatically created the A records, etc. that would be needed. And virtually every client I would have around here would desire and require my handling of those matters. I don't anticipate this being a completely automated system for allowing clients to setup their own sites, and handle their DNS, etc. That would take me out of my "custom site" niche and be quite complicated, as well... I would also be using their login information to determine the client using the CMS and then their database name would be looked up in a central database for the CMS app and their database name would be assigned to a variable to be used throughout the CMS process. Looked up once in a query, then assigned to session variable, like Session.Database. I found out last time I tinkered with something like this not to assign any values to application variables, since they are shared with all users in an app, and to use session variables, instead. Sound good? Rick -----Original Message----- From: Casey Dougall [mailto:[EMAIL PROTECTED] Sent: Saturday, December 02, 2006 2:49 PM To: CF-Talk Subject: Re: Advice needed on how to proceed with app... Be careful of wildcard settings on your sites. Yeah it's cool but Search Engins do not like it at all. The problem stems from Google, yahoo etc thinking there are more than one website with the exact same content. This of course means when someone goes to domain1.thedomain.com or domain2.thedomain.com they view the same index.cfm page as domain3.thedomain.com. Now of course if you use some #CGI.SERVER_NAME# lookups first, then set the content of index.cfm to match the domain in question you could be ok. You can even use wildcard for any site name, right... When a user registers to use your app, they get a pre-maid subdomain name from you and they can enter a domain name in their preferences and setup an "A" record that points to the IP address of this site. #CGI.SERVER_NAME# does a lookup on your customer table for the domain name and if it finds it with or without www. it's routed correctly. -- Casey ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:262626 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
