After descending on Mallorca last week for our twice-yearly team retreat, the Railway team spent this week dispersing back across the globe to our homes.
Since we took a couple of days for travel and rest after the retreat, the changelog is running on a limited local schedule this week — in addition to a number of small quality of life improvements, we’re also shipping some modest but choice improvements to the API, OOM notifications, and the CLI.
Like last week, we’ll also remind you that we’re hiring for exceptional Product and Infrastructure engineers. If that sounds like you — and you, like us, are obsessed with the intersection of distributed systems computing and interface design — please reach out.
Now let’s get into this week’s changelog.
All aboard!
Private Registry API Support
Four weeks ago we shipped support for private registries to Pro users.
This is an important feature for advanced users and those who need to define and deploy images with private credentials from container registries like GitHub or DockerHub (or Quay.io).
This week, by user request, we shipped API support for private registries.
With this improvement, it’s now possible for Pro users to access private registries programmatically via the Railway API.
To get started, check out the docs and/or the GraphQL playground.
And if you have a comment or suggestion for how we can continue to improve either private registry support or API support, be sure to spin-up a thread in the forum and let us know.
Thanks!
Out of Memory Email Updates
Nobody likes running OOM, but now we’ll send you an email notification when we detect that your deployment has maxed out its mem.
The email will let you know the specific project, environment, and service has run out of memory and will even link you directly to the deploy logs.
Nice!
But what’s that, you say? This notification isn’t quite what you need? Please let us know what else you’re looking for as we’re going to be diving deeper into notifications this quarter.
Thank you!
Feedback Welcome
Notice a trend in this changelog — asking for your feedback?
Well let’s make it official.
We’re once again asking you to let us know in the Help Center what you need to be successful on Railway.
Your feedback is absolutely essential and although it always matters to us, the beginning of the quarter (like right now) is an excellent time to provide feedback because we’re still doing a small amount of planning as the quarter gets underway.
So with that said, we invite you to open a thread or comment on someone else’s thread with your most burning Railway need — we appreciate it already.
See you next week!
Fixes and Improvements
- A big thanks to Community Member Milo for contributions to the CLI including adding support for template-powered databases. Thank you Milo!
- We made some improvements to the way we display settings in public projects
- We no longer sync branches across environments when syncing staged changes
- We fixed a small issue with the Template Composer
- We reduced the destructive changes capabilities of non-admin users
- We improved the workflow when transferring a project to a team
- We now allow mounting a volume to subpaths of
/etc