[Reactor for CF] Using Reactor on Live Sites

[Roy Martin]

In short: How do you manage your reactor drops across multiple projects and keep reactor up to date?   Overview: I’ve been using reactor sparingly on a couple of sites on our live server but now I have two sites in development stage that are heavily relying on reactor. In the past I had simply mapped everything to one reactor folder and run test on all of our websites to ensure that upgrades to reactor didn’t break them. Unfortunately I hadn’t updated reactor in a while because I hadn’t pushed it far enough to run into any bugs, I finally did and ran an upgrade. Unfortunately, it broke these two sites so bad I had to fall back to another version. Some functionality changes, some architecture changes that threw random errors.   So the only solution for now it seems as I use reactor during the beta stages is to copy a folder of reactor into each project launch because if the entire site works and has been through ally tested using this version. I hate the idea of multiple frameworks running around especially if problems arise later and I’ll have to figure out what I can and cannot do in that version, but there doesn’t seem another way to sanely maintain releases and not spend hundreds of hours fixing old sites with old reactor code.   Any thoughts or better suggestions? I understand this is what I get for using Beta software, I’m not complaining just want to know how to use it and not get burnt.   Thanks, Roy -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List reactor@doughughes.net Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --