littlelogs

Keep a social journal of your work progress as you make and learn things.

larouxn
larouxn

Been diving head first into technical #midnightmurderparty stuff for the past two days. Yesterday I attempted to upgrade our stack to Ruby 2.3.3, from 2.3.1, but ran into some arcane gem errors. Might have to fork a gem or two if this keeps up. For now, we’re staying on 2.3.1

Aside from the Ruby version update shenanigans, I implemented some nice error handling on the backend. Now if an HTTP error code is thrown (server error), I will be emailed. Nice for when we go live as I’ll know if anything breaks, when it broke, and what the error was without having to anymore than check my email. Also, spiced up (improved) our logging so we know everything that goes on from regular functionality to errors and beyond. Getting close to beta time! 🙂