Updating Heroku migration guide #2347
Conversation
theoctopusperson
commented
Feb 11, 2026
theoctopusperson
commented
- Replace Rails-specific migration doc with a language-agnostic guide covering Node.js, Python, Ruby, Go, and more
- Add new doc at /docs/getting-started/migrate-from-heroku/
- Remove old doc from /docs/rails/getting-started/migrate-from-heroku/ with redirect_from for backwards compatibility
- Add sidebar nav entry under Getting Started
- Replace Rails-specific migration doc with a language-agnostic guide covering Node.js, Python, Ruby, Go, and more - Add new doc at /docs/getting-started/migrate-from-heroku/ - Remove old doc from /docs/rails/getting-started/migrate-from-heroku/ with redirect_from for backwards compatibility - Add sidebar nav entry under Getting Started Co-Authored-By: Claude Opus 4.6 <[email protected]>
theoctopusperson
changed the title
jphenow
left a comment
jphenow
left a comment
There was a problem hiding this comment.
Probably wise to take out some of the pricing but maybe its still useful to explain how our usage works differently and point to /pricing or the docs for pricing?
kcmartin
left a comment
kcmartin
left a comment
There was a problem hiding this comment.
I know there's been resistance to entirely removing pages for SEO reasons -- wouldn't the redirect accomplish what you're after,without needing to remove the Rails page? Do we care to provide any Rails-specific info in the new guide?
Info on redirects: https://github.com/superfly/landing?tab=readme-ov-file#redirecting-pages
- Add illustration back (Annie Ruygt migrate.png) - Add pricing paragraph with link to fly.io/pricing - Add CLUSTER_ID reminders and fly mpg list fallback - Add warnings not to commit secrets files to git - Fix fly open → fly apps open - Fix [[services]] → [http_service] format - Remove invalid maintenance mode link Co-Authored-By: Claude Opus 4.6 <[email protected]>
Co-Authored-By: Claude Opus 4.6 <[email protected]>
|
@kcmartin Re deleting the old page, the redirect totally does accomplish the objective, but the old page is so outdated I felt like it's not worth even risking a user landing on it somehow (even if that makes an SEO dent). Happy to add it back if anyone feels strongly. |
3 participants
