littlelogs

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

larouxn
larouxn

Over the holidays, as I wrote in my last log, I tried to upgrade #midnightmurderparty to Ruby 2.3.2 and then 2.3.3 unsuccessfully. Well, 2.4.0 was released on Christmas and I failed to upgrade to that too.

Unfortunately, it seems the combination of one of our unmaintained gems, rvm/rvm1-capistrano3, which manages installing our gems and selecting our Ruby version during deploy and our one GitHub hosted (not RubyGems) gem, seuros/capistrano-puma, does not want to work with Ruby above version 2.3.1. It seems either I switch off RVM, originally I used ruby-install and chruby but couldn’t get deploys working, or I fork this GitHub gem and push it to RubyGems. Neither are guaranteed to work and both would kinda suck.

Aside from that, I’ve been fine tuning our error emails and finding out firsthand that a lot of random bots on the interwebs crawl your site and request nonexistent, usually PHP, files. Trying to keep from waking up to 10 ERROR 404! emails. 😅

josh
josh

Ugh, that sucks. That’s why I haven’t bothered upgrading anything serious from python 2.x to 3.x, because it’s such a drama.

I’d turn off 404 emails for that exact reason, there are too many bots. Django currently notifies me when someone tries to access the site via a different Host header (usually the IP address instead of the domain name) which I get regularly and is so useless, but I haven’t figured out how to turn just that error off.

04 January

larouxn
larouxn

Yep, yep, good idea. I did just that right after I posted this. No more 404 emails. 😌 As much as I want to upgrade the Ruby version, there are more pressing matters like how the Blink engine was updated a week ago and every Chromium based browser stopped rendering all pages after page 2 in our reader… 😒

04 January