Hello everyone, this changelog will be about new features that make it easy for you to migrate from Heroku to Railway.
Auto Create Services from Procfile
Railway now detects if there is a Procfile at the root of your repo. Then we map each Heroku process within the Procfile into a service. We even carry over the name of the process from the Procfile to your new project. That easy! We also made a bunch of resources to try to convince you to move your project over. Let us know if it’s successfully convincing.
- railway.app/heroku
- Migrating from Heroku to Railway blog post
- Differences between Heroku and Railway docs
- Import variables from Heroku docs
- Convert Heroku app.json to Railway template
We also have a great Discord community where you can come and ask any questions you have.
Import Variables from Heroku
We’ve made it super easy to import your config secrets from any existing Heroku apps. On the service variables page open up the command palette (⌘+K) and “Import variables from Heroku”. The first time you do this you will need to connect your Heroku account. When importing, if a variable already exists for your service then it won’t be added. So you don’t have to worry about overwriting anything.
Heroku app.json to Railway Template
If you already have a repo that contains a Heroku app.json schema, you can convert it into a Railway template with the click of a button. Just head to railway.app/heroku-to-template, enter your GitHub repo, and we will autofill the template form with everything that maps over to Railway. You can create the template and save to your account in 1-click.
