> The reason I don't go to a virtual server ("site" in IIS) at
> first is to avoid having to use Host Headers and expose the
> site to the public via the domain name before it's complete.
> Usually, I would just tell a client to go
> http://66.xx.xx.79/cfdocs/yoursite/index.cfm to view their site.
>
> Looks like that'll just change to telling to go to
> http://www.DefaultWebsite.com/yoursite/index.cfm, which will
> work the same, promote my website (when I finally build it!)
> and be easier for the client to remember.
>
> Does this sound like it will work well?
You don't have to expose anything to anyone you don't want to, whether you
use virtual servers or not. I guess my whole point here is just to mention
that it's good to have your development environment mirror your production
one as much as possible. In production, presumably, that client's content
will have its own virtual server, and won't be a directory within a virtual
server.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Software provides the highest caliber vendor-authorized
instruction at our training centers in Washington DC, Atlanta,
Chicago, Baltimore, Northern Virginia, or on-site at your location.
Visit http://training.figleaf.com/ for more information!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195814
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
