Re: [Reactor For CF] Problems with configuring reactor for shared environment

[Jared Rypka-Hauer]

You're wrong on the first point... In production, the application lives at http://www.hostname.com/index.cfm. In dev, the application lives at http://localhost/siteName. First of all, I think this is something almost everyone has gone thru at some point. Second, it creates a fundamental issue that, until now, he's been able to get around by using application variables to store path and mapping information so that the applications can find their parts on either server. However, when you're dealing with CFCs you cannot use variables to control where the server looks for the files! "Path" and "type" are the same thing... i.e. returntype="reactor.ReactorFactory" is a path AND the type of object you expect to be returned. This precludes any dynamism since returntype and cfargument type="" expect static strings. The easiest and simplest alternative here is to put the applications on the production server in a subfolder of the root with the same name as the folder it lives in on the development server: http://localhost/app1 http://www.prodserver.com/app1 That way, you can have any number of application folders in your root (and name them appropriately per-project or customer, but keep them consistent across all servers). You can have Reactor in the root of the server (basically at http://www.prodserver.com/reactor), MG, ColdSpring, any anything else in the root. If you have a main app that everyone gets routed to if they go to http://www.prodserver.com, use an index.cfm with a cflocation tag in it. As an example of how well this works, go to http://www.web-relevant.com and watch the URL... I have a fusebox application that uses fb4.1, Tartan, and a whole bunch of hand-coded CFCs on a shared server. Since the application itself is at /web-relevant (where the redirector pushes you) I can also have it (and about two dozen other projects) in the webroot of my single development server that runs on the Jrun built-in webserver. No problem... works a champ. At the very most, you want a mapping to the root of your website, but I have no mappings on any of my boxes because in the absence of a mapping, / works out to your URL with nothing after it... so reactor.reactorFactory points to /Reactor which is in the webroot of my application. Maybe this stuff is easier for me because I spent 8 years in LAN and server support, so routing, server technologies, paths, virtual paths, and all is just sort of second nature. I'm trying to explain it as clearly as I can... I hope it's being helpful. Thanks, 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 On Apr 16, 2006, at 5:44 PM, Matt Williams wrote: As I understand, Mike is using a development machine to emulate his shared server. I haven't read all posts thoroughly, but I don't think Mike has answered a simple yes or no to. Can your shared server put a Reactor directory under the web root (not the web site root, the web root; for IIS, it is usually inetpub\wwwroot)? If yes, then you do not need a mapping. <cfelse>, your options are: 1) Begging the hosting company to let you put a Reactor director under the web root. 2) Create a mapping for each site you put Reactor within that site 3) Edit the Reactor code to refer to the siteName.Reactor. Doug, or somebody, correct me if I'm wrong on his options based on his answer. -- Reactor for ColdFusion Mailing List -- reactor@doughughes.net -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/