> In a shared hosting environment this is the approach I use. > It allows me to move the site to any server and just add a > single mapping and not worry about any other paths. > > For the site: > http://www.somesite.com > > webroot: d:\sites\somesite.com > > I create a directory where I place all of my components, > custom tags and include and create a mapping to that directory > > components & tags directory: d:\sites\somesite.com\somesite\
If possible, you might want to reverse this structure: Webroot: d:\sites\somesite.com\webroot Components & tags directory: d:\sites\somesite.com\ This would limit what exactly is directly web-accessible to the minimum amount required, and would avoid any potential security ramifications of having those other things web-accessible when they needn't be. Unfortunately, I have no experience with shared hosting, so I don't know if that's possible. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
