How I migrated a multi-tenant Rails app from Heroku to Railway in about an hour, including the part where I accidentally broke the database.

The RubyLA blog offers insights, tutorials, and community updates for Ruby developers in Los Angeles and beyond. Developers can explore Ruby language features, web development frameworks, and best practices for building Ruby applications. Additionally, the blog covers Ruby meetups, events, and job opportunities in the Los Angeles area, fostering collaboration and networking within the local Ruby community.

RUBYLAND

A developer migrated a multi-tenant Rails app (5 hospitals, 25K+ appointments) from Heroku to Railway in about an hour. The post covers the full process: capturing and restoring a Postgres database, handling the heroku_ext schema extension issue, an accidental incident where running 'railway up' without --service replaced the Postgres container with a Rails web server, DNS configuration for wildcard subdomains, fixing a RACK_ENV misconfiguration, and a pricing comparison showing Railway is slightly cheaper. Key lessons include always verifying row counts after restores, always specifying --service in Railway CLI commands, and being aware of Railway's trial plan limitations. The post also includes a fair warning about reported performance and reliability issues on Railway for larger workloads.

Migrating a Rails App From Heroku to Railway - FastRuby.io