I'm unfortunate enough to be stuck with a Rails project from the '50s. It's based on RoR v1.2.6 and is using about 20 odd plugins and a huge assortment of gems - all of which scream bloody murder if I attempt to upgrade the project to anything >=2.x.
I managed to get the site to just start up by removing 50% of the code. I'm going to need to spend a while slowly bringing stuff in and fixing what breaks. At this poing it's going to take a week or two to bring it all back in and get it working.
It's tempting to slowly remove a lot of the dependencies (the previous developer seemed to want to implement ALL of the site from a patchwork of third party plugins) and then attempt an upgrade to v2.0, then to v2.3.5. At this point I should probably just wait until Rails 3.0 is out of beta.
Not that I have the time ofcourse.
I managed to get the site to just start up by removing 50% of the code. I'm going to need to spend a while slowly bringing stuff in and fixing what breaks. At this poing it's going to take a week or two to bring it all back in and get it working.
It's tempting to slowly remove a lot of the dependencies (the previous developer seemed to want to implement ALL of the site from a patchwork of third party plugins) and then attempt an upgrade to v2.0, then to v2.3.5. At this point I should probably just wait until Rails 3.0 is out of beta.
Not that I have the time ofcourse.
Comments