– Motivation for switching from PHP to Ruby on Rails

– Figuring out which gaming API to implement first and how their APIs are

– Reverse engineering undocumented API calls from the Windows Steam client

– Using a separate database for each gaming platform provider

– A few useful features of Rails that’s being used and Stimulus Reflex

– Switching from Webpacker to using Vite

– Using Slim instead of ERB and a few other gems being used

– It’s a single monolithic Rails app that’s using namespaces

– A lot of the time spent developing this app is working with the game APIs

– Using Sidekiq, a billion (!) gamer activities stored and millions of Sidekiq jobs

– It’s hosted on a single AWS T2.large instance (4 vCPUs / 16 GB memory)

– The database is on an R6g.large with 10+ billion records

– Ansible was used to set up the EC2 instance and it’s running Ubuntu 18.04 LTS

– A couple of AWS resources being used

– The process to ship a feature from development to production

– Switching to using TailwindCSS in a nicely controlled way

– At the moment the site is free with no desire to make it pay to win

– Hosting is $1,500 pounds a month and it’s been running for free for 7+ years

– There’s 7 terabytes of S3 storage and daily database backups

– 50ish mini servers spread across Heroku’s free tier to bypass API rate limits

– Being dialed into the ops side of things but there’s room for improvement

– Keeping up with a full date job and a long running passion project

– Best tips? Don’t forget to plan things out

– You can find Vlad on Twitter and Games Directory will be open source soon