Hosting RydersWorld on Its Own Heroku App

RydersWorld runs as a completely separate Heroku app from getawd. Same AWS account, same Route53 zone, different app, different dynos, different pipeline. I added a custom domain in Heroku (rydersworld.getawd.com), grabbed the DNS target it generated, and pointed a CNAME at it from Route53. That is it. Once DNS propagated, Heroku handled SSL automatically and the app was live on its own subdomain. No shared codebase, no shared database, no weird routing tricks. Just clean separation. It keeps production concerns isolated, makes deployments safer, and lets the project grow without touching the main site. Simple setup. Boring infrastructure. Exactly how it should be.