Mike,
About possible reactor core updates, it can happen since we’re
still in alpha. What I usually do is to get a version of reactor and copy it to
that website root folder and always work with that version. If reactor core
files are updated, It won’t break my previous work. Well it’s quite
crazy having several versions of it but it’s also challenging. I prefer
like this. Of course it would be great that all apps could use always the
latest version of reactor but I’m aware that’s still in alpha so, I
have to live with it.
For the Webserver part, since I use a dev box (win2k server) I
don’t have this kind of problem. When I use my laptop for development I
just use IIS 5.1 with a single website. IF I had your problem, I’ll would
have 2 possible options:
1)
Apache
2)
ColdFusion developer edition in multiserver
install.
For option 2) I
would create different instances for each site and set them all to start manually.
And deploy my website inside my cf-instance webroot folder.
João Fernandes
Dep.
Informática - Área de Desenvolvimento
Cofina media
Avenida
João Crisóstomo, Nº 72 . 1069-043 Lisboa PORTUGAL
Tel
(+351) 213 185 200 . Fax (+351) 213 540 370
[EMAIL PROTECTED]
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Mike Kear
Sent: segunda-feira, 17 de Abril de 2006 10:18
To: [email protected]
Subject: Re: [Reactor For CF] Problems with configuring reactor for
shared environment
The outcome:
For the longer term I think i have to change my web server, probably to Apache
and reconfigure all my existing sites to work with that, progessively as I do
work on them.
In the short term, I'm going to have reactor in its own folder at c:\inetpub\wwwroot\reactor and
have to remember to upload the reactor folder as well as the site when I
upload. This will work until the inevitable day arrives (as
murphy's law says it will) when there's some kind of upgrade or change to the
reactor code that requires a change to the application code.
Here's how I think my options boil down:
[A] have a single reactor folder with core files, under the web
root, but outside any of the sites using it. When I upload a site,
I have to remember to also upload the reactor folder. Pro: easy
to do, and will work, at least early on. Con: with
so many sites, every time there's a change to the core code all the sites that
use it will have to be retested. Initially, with maybe 5 sites using
reactor not a big hassle but as more and more sites start using it, will become
more of a task. Con: if
there's ever a new version of the core code that requires different application
code, that will cause problems. (the same comments apply to MG and
Coldspring)
[B] go into IIS and change the location of the web root every time I change to
working on a different site. Pro: quite
easy to do, and gets around the Cons in option A. Con:
I quite often do work on several sites in a day and that is a lot of mucking
about and will soon become REALLY annoying. I have had 6-7 sites
worked on in a morning when I do small updates.
[C] Use the CFMX built in web server instead of IIS. Pro:
not sure what it offers over IIS, but I think it's easier to change the web
root. Con: same as B - a lot of mucking
around each day.
[D] Change my dev web server to one that allows multiple sites, e.g.
Apache. Pro: makes the problem go
away, since any number of versions of reactor and mg and coldspring and
anything else that might take my fancy can coexist without colliding with the
others. Con: in the short term, I'll have a
lot of work reconfiguring all the dev versions of my sites to work with
it. Con: while a lot of people
have said its easy to install and administer, I have found the documentation
pretty impenetrable in the past. I found apache installs and works fine, but
understanding what to do to configure it wasn't as straightforward for me as
other people found. And when I asked questions about it, instead of
getting answers to my questions I got a succession of "it's
easy" and "it works for me" and "read the docs"
rather than answers. I would need to allow quite a bit
of time for figuring that out. (this is something else I'll be criticised for
no doubt)
Are there any other options I've missed?
At the moment I'm thinking I'll go with [A], with the knowledge that it's going
to bite me one day and hope I can get [D] completed before option [A] comes to
bite me.
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
-- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
-- Reactor for ColdFusion Mailing List -- 
