Railway
← All Updates
CHANGELOG

Changelog #0105

Follow us on X

Double, double toil and trouble, the AWS bill burns and the cauldron bubbles … that Shakespeare fellow, so ahead of his time, crazy to think EC2 was only just released when he wrote that! 🧙‍♀️🎃

Buffs to Config as Code UI
Untitled
Untitled

Last week we introduced config as code to Priority Boarding users. This week we added a new view to the deployment details page that generates the config for you!

If you’ve already added a config file, we’ll now provide a handy link to edit that file in GitHub. Either way, we’re going to make sure it’s easy for you to start versioning your configuration settings.

What else can you do with config as code? Maintain distinct environment settings, enable distinct pull request behavior, generate reproducible Railway templates, on and on and on. It’s exciting stuff. Would you read a blogpost about this? So would we. Ok, fine! We’ll write it!

PR Environment Override
Untitled
Untitled

Since all our homies hate it when they PR something and the config settings don’t come through, we added support for overriding the environment when deploying via pull request.

The priority order for resolving service configuration from a file is now:

  • Environment with the name of the ephemeral environment
  • Environment with the hardcoded name: "pr"
  • Base environment of the pull request
  • Base config as code
  • Service settings

Read the docs for more info.

Heroku Buildpack Deprecation Reminder
Untitled
Untitled

Ever since the Heroku Buildpack Deprecation announcement we’ve seen a large number of users swap over to Nixpacks from Heroku. We know that bugs can still be hiding so keep the reports coming if you run into any issues.

Otherwise this is a Public Service Announcement to please cut over to Nixpacks if you’re still using the Heroku build-packs.

builder-nixpacks.png

Pro tip*:* You can change the builder within the settings tab of your service under the Build menu.

You have until November 14th until we cutover all projects to Nixpacks on your behalf.

Improvements and Fixes
  • Nixpacks upgraded to v0.11.5
  • Fixed an issue with Nixpacks where it would fail if you had a non-standard value for the workspaces key
  • Now prefer the web process type as the start command
  • Now support specifying a node version within a .nvmrc file
  • Fixed some confusing copy when a deployment succeeded
  • Fixed an issue that sometimes resulted in custom domains routing incorrectly
  • Fixed a bug that sometimes caused the Railway dashboard to flash when navigating
  • Improved the rate limiting logic associated with creating new projects — sorry for the bug!