Resurrecting an old app
Today I did some work upgrading an old application to Rails 4 / Ruby 2. It was reasonably easy and there were only a couple of gotchas.
Rails 4 no longer uses the mass_assignment_sanitizer so I disabled any attributes set in the model, removed the config element and, well, it worked, which is kind of worrying because I want the attribute assignment to be protected but for no - it’s not - something I will have to return to.
Postgres installation on Mac OS hasn’t got any easier - actually this has nothing to do with a Rails upgrade and everything to do with working on my own machine rather than a corporate laptop. Which is a lovely feeling and deep mountain crevasses away from being a gotch.
So the app is resurrected and may well form part of my MVP.
I spoke too soon. Way too soon. The upgrade to Rails 4 was suitably painful - in accordance with a full version bump. But I didn’t know it at the time.
rspec spec, got the green light and whoosh - push! But forgot that way back when I build this app, the functional tests were in cucumber. That broke everything. Fortunately. Now it’s mostly fixed. Well
rake runs green.
Let’s see what happens when we deploy. I predict some asset pipeline hell.