At 5/7/2000 01:09 PM -0700, paul smith wrote:
> >Mostly because I then don't have to worry about where a template/page
> >lives in the dir structure (in terms of it specifying IMG sources and
> >such). Also because I like to create my development environment to
> >precisely match the deployment env., and that means separate roots.
>
>Please clarify. "match" & "separate" don't appear to agree.
Mmmm... I want my development env. to match my deployment env. and that means separate
roots for each site I'm working on (ie. www.this.com has a different root from
www.that.com). Clearer?
>And are you using CF absolute paths, or web server absolute paths?
>(Which gets me to a question I recently asked here about accessing CF
>templates across the LAN.)
I'm talking about paths as they would appear to a browser. On a bigger project I tend
to use CF mappings and absolute paths as well, for includes and such. I also like to
set a global variable which points to the physical root of the application
(d:\webs\myapp\) for use with things like CFFILE, etc.
Cheers,
-Max
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
