+1 for per-application mappings. You can even get fancy and set it it based on cgi.server_name or path_info so you don't have to change the code between dev and production. Note, for this to work, dev and production need to be in their OWN application.
A better solution would be to actually have a dedicated box for your dev server so you can do testing there without fear of ruining your production server's stability. There are also settings I enable on a production server like Trusted Cache that you wouldn't be able to use for a dev server. If you can't spare a separate box, AT LEAST create different sites for dev and production on your server with their own completely separate web root. www.mysite.com and devwww.mysite.com. If you are running CF Enterprise in multi-server mode you can actually have separate instances for dev and production which is the next best thing to a different physical server. Ok, actually a VM is the next best thing to that, but I digress... ~Brad -------- Original Message -------- Subject: Re: How do I solve this path issue for components? From: Sean Corfield <seancorfi...@gmail.com> Date: Tue, June 08, 2010 3:34 pm To: cf-talk <cf-talk@houseoffusion.com> Why not use per-application mappings? In Application.cfc, you can set this.mappings[ '/mysite' ] to either the production or dev CFC root as needed... On Tue, Jun 8, 2010 at 1:03 PM, Rick Faircloth <r...@whitestonemedia.com> wrote: > > Hi, all. > > > > I've started using two different folders on my servers for each site. > > The first is for viewing a site online during development and the second > > folder is for production. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:334375 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
