If you're not willing to be flexible then we can't help you. I don't care how you set up your development environment. We're all trying to show you how it could work, but you're ignoring it. If you don't want to fix the problem then stop bitching about it. Move on and do it the old fashioned way.
For the record, you could use IIS admin to create 42 different iis entries in iis 5.1 and then you wouldn't need to worry about this mubmo jumbo. It's your choice not to and you suffer the consequences. The concept that Reactor should somehow compensate for your technique of using application variables (which reactor should be agnostic to) is offensive. Here's a 30 second solution to your problem: 1) create a mapping on your dev cf server pointing to reactor. 2) when you move the site to production place reactor under your webroot. Doug -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Kear Sent: Sunday, April 16, 2006 12:26 PM To: [email protected] Subject: Re: [Reactor For CF] Problems with configuring reactor for shared environment At last you're getting to the nub of the issue, and at last you've started to see what my problem is. For all of my 42 sites, that system works fine. I have an application variable in all my sites called #application.approot# and another one called #application.appmapping# and on all of my 42 sites until now, that has proved viable. All links and references either use relative links, or if i want to use absolute links (e.g. in a header include because it can be called from any point in the site) i use something like <cfinclude template="#application.appmapping#/includes/header.cfm" /> All of these sites work fine, and I can click on either the local version http://localhost/companya/index.cfm or the production version http://www.companya.com/index.cfm and get identical results. The file layout is identical relative to the top level application.cfc of the site, so I dispute that it is 'flaky" as you say. I've seen far more "flaky" environments in my contracting work. Some of the dev environments bear little similarity to the production environment. It's proved rock solid for a couple of years now since i started doing it this way. And I have 42 sites of varying complexity all using something similar. I KNOW I'm far from alone on this. If i did all my work sitting at the same desk plugged into a server, I'd probably have it the same as you. But i do a fair amount of my work sitting in the train with the notebook on my lap. I need to have it all working in the same box. Until now everything has worked fine, and I know a great many developers do the same thing as me. I've seen some of them working on the same train. What I think needs to happen is one (or more) of the following: [A] a note added to the Reactor docs that if using WinXPPro and IIS6 there might be issues and preferably with some ideas about how to get round them. [B] a way be devised that Reactor doesnt have to be at the root of the site, [C] a way be devised that Reactor can work with any mapping not just "Reactor" (I know that both B and C are not trivial, but it would be good if they could happen at some point) Cheers Mike Kear Windsor, NSW, Australia Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month On 4/17/06, Jared Rypka-Hauer <[EMAIL PROTECTED]> wrote: > 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 -- -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
