4 ms·
For 6 years I’ve been building Cronitor.io with my best friend and business partner, August. We started on Django 1.6 and I’ll admit: we liked it so much we st
by encoderer 6y ago
For 6 years I’ve been building Cronitor.io with my best friend and business partner, August.
We started on Django 1.6 and I’ll admit: we liked it so much we stuck with that version for 5 years (ha ha).
Earlier this year we did the mythic trek to Python3 and are enjoying the all the new Django goodies.
August is working full time on Cronitor but for me it’s still technically a “side project” — for now!
Edit: sorry for the dupe! August already posted here.
- japhyr 6y ago> Earlier this year we did the mythic trek to Python3 and are enjoying the all the new Django goodies. Can you share anything about how that upgrade journey went? What are some of the newer features that have been helpful for you? Were those features you knew would be helpful, or were you happily surprised?
- encoderer 6y agoI didn't do much of the actual coding on that project but from my perspective the upgrade on our Django app went smooth. We were excited to have Django Migrations (So long, South!) and honestly it's great to have access to current docs again. We did have a snag with memory leaks in a threadpool in one of our non-django Python APIs. It was actually our worst outage in 5 years because it failed several hours after we deployed and we were no longer staring at our graphs. (Maybe I can get August to write a blog post about how he accidentally sent a million emails to our personal inboxes while trying to clean that up)