Mike,

You're trying to equate websites in production with subfolders of a webroot in development. This is, as you say, a recipe for disaster. If, for instance, you're trying to do a customized version of Application for companies A and B at the same time, obviously in prouduction you have http://www.companya.com/Application and http://www.companyb.com/Applicaiton. What you're trying to do is set your development environment up so that you have http://localhost/companya/application and http://localhost/companyb/application.

Now, if you have Reactor at c:\inetpub\wwwroot\reactor, both applications can use it... however when you go to move from dev to production, any includes, CFCs, etc, will be at a different location than they were when you were developing... which, I understand, is the problem. This however has naught to do with shared environments but with a really flakey development environment setup.

You can't treat "wwwroot/site1" the same as www.site.com unless, as with my site at www.web-relevant.com/ you put site1 at /site1 in the production environment too (which is how I overcame the problem once upon a time... http://www.site1.com/site1, http://www.site2.com/site2, http://www.site3.com/site3... get the pattern? ;) ), however ModelGlue and Reactor and everything else can still go at /Reactor, /ModelGlue, etc., because those are shared amongst all applications on the server and HAVE TO BE at /.

HTH,
J



------------------------------------------------

Jared C. Rypka-Hauer

Continuum Media Group LLC

http://www.web-relevant.com

Member, Team Macromedia - ColdFusion


"That which does not kill me makes me stranger." - Yonah Schmeidler

Reply via email to