So in a bout of update frenzy I’ve accidently upgraded my system Ruby to 2.2 and decided to use this as an excuse to test Discourse with
ruby 2.2.0p0 r49005.
Right off the bat, I have to make two changes to even get Discourse running:
change(Actually, this change made it into
Gemfile.lockto use version 1.8.2 of the
jsongem. Version 1.8.1 was moved into Ruby’s stdlib, the native extension for the 1.8.1 gem won’t compile against the Ruby 2.2 C API.
masteronly hours ago. )
UNICORN_ENABLE_OOBGC=0in the environment to disable out-of-band gargabe collection in unicorn in production. According to this, Ruby 2.2’s incremental GC makes oob GC largely unnecessary.
Apart from this, things seem to be stable at first glance, but I’m definitely going to have a close look at my error logs and performance counters over the next few days.
All in the name of not admitting a mistake and just downgrading back to Ruby 2.1…