#Tag
As if Jeff wouldn't immediately turn over every single piece of data he has on me to the highest bidder and/or whichever police state he is trying to cosy up to
(and yes yes, before any "just use «X»", I am only in here to migrate *off* AWS – back on #Levelfly development for a minute 😎)
#Levelfly #Ruby / #Rails upgrade 2026 update: we Put Together a team! 🤩
Delighted to be linked back up with one of the CUNY / BMCC academics who originally initiated (and is still using) Levelfly, and a seasoned tester & project manager from Neuronic. We're full-tilt to try and get this update finished in time for the next cohort of students who will be using the software soon.
I'm 90% sure that extending the test suite will smoke out other problems introduced by #Rails / #Ruby upgrades that I hadn't caught yet.
Of course, building a more comprehensive suite back on day 1 (Rails 4.2 😬) would have mitigated this – but I was really struggling with dependencies on such old versions of Ruby and Rails, keen to start making progress – and I was satisfied that 40% coverage was better-enough than 0% to get on with it.
After that, I want to focus on the #Docker image.
Somehow – despite applying a couple of Dockerfile tricks I've picked up since my last #Levelfly containerisation work back in 2021 – the image has ballooned from 400MB to 1.8GB, and I'd like to get that back down to size.
Part of this will likely involve publishing separate "development" and "production" images, to save new project contributors from a docker build process.
