Extra, extra, read all about it! 🗞️
News is breaking left, right, and center this week, folks.
This past week, our industry saw not one, not two, but three, at least, major clouds have major outages.
It was an eye-opening reminder to us to remember to be really, really careful with upstream platform dependencies. And it’s also a reminder of why we’re exiting the public cloud and migrating entirely to Railway Metal — because we believe that You Can’t Build a Cloud on Another Cloud.
With that said, we have quite a trove of stories to run during an otherwise tumultuous week.
Let’s start peeling these pages off the press!
Last Call to Migrate to Railway Metal
Six weeks ago, we told you the gentle nudges to migrate to Railway Metal were giving way to stern reminders.
This week, we’re letting you know that this is the last call to migrate your workloads to Railway Metal before we migrate them for you.
You may notice already that non-Metal regions for Southeast Asia and US East have already been deprecated — next up, we’ll be deprecating non-Metal regions for US West and EU West.
This means that if you still have workloads on our legacy GCP instances, they will shortly be moved for you. If you’d like to avoid this, please move them now. (Thank you!)
If you have questions, please read the docs.
If you’d like help migrating to Railway Metal, please file a ticket.
We’re here to help. 🫡
Community-nominated Bounties
We’re extremely chuffed about the early returns on Railway Bounties.
As a reminder, Bounties is a way for you to get rewarded for answering questions from other Railway users or authoring templates requested by the Railway Community.
This week, we’re excited to open up the bounty request system to you, our loyal reader. This means that you can now submit your own bounty request — and if we like your request, we’ll fund it and add it to the community bounty list.
To get started, head over to Central Station and click on the New Bounty button.
Onward!
Teardown Services with Config as Code
It’s been a while since we’ve talked about Config as Code, but we wanted to let you know about a couple of improvements we made this week.
It’s now possible to define deployment teardown settings … in code!
This means you can specify Overlap Seconds, which is the amount of time that a previous deploy will overlap with the newest one being deployed, as well as Draining Seconds, which is the amount of time between when the previous deploy is sent a SIGTERM to the time it’s sent a SIGKILL.
For more Config as Code capabilities, check out the reference page.
To request more Config as Code capabilities, drop us a line in Central Station.
Take us home!
More RAM for Trials
We increased the RAM available to brand new users on the Trial plan to 1GB.
Previously this was limited to 512MB, but that was preventing some templates from running — which was creating a bad experience for template creators and users alike.
So we bumped the limit — tell your friends! We hope they like it.
Thanks for reading and have a wonderful weekend. 💖
Fixes and Improvements
- We made improvements to deployment dependencies so that queued items will resolve faster
- We added the ability to remove credit cards from your account (at last!)
- We improved monorepo build speed in Railpack
- We added support for Go workspaces (
go.workfiles) in Railpack - We also want to shout out Railpack contributor FugiTech for improving Elixir install speeds!