Welcome to the changelog, y’all.
It’s been a quiet week over here as we’ve been heads down finishing out the quarter and preparing for Q4 planning, which is next week. The week after that, we’ll be heading off to the Greater Chicagoland area to sample deep dish pizzas and spend time together during our biannual retreat.
Oh! That reminds us — we’re looking to add a few more talented Infrastructure and Product engineers to our team before the end of the year.
If you or someone you know might fit the bill, please reach out and say hello. We look forward to meeting you.
Ok! Now let’s turn down the lights, turn up the music, and get this thing started.
Last Chance for Nits
Since we mentioned quarterly planning is next week, let’s talk about the easiest way for you to influence our roadmap for next quarter — the Nits Superthread!
We introduced this thread a few weeks back and invited you to tell us about all the little things on Railway that bother you and/or the features that you’d like us to implement.
The response so far has been excellent.
We’ve stack-ranked all your requests and have already implemented a large number of fixes and improvements. (And yes, we hear you on SSH, we’re planning to work on it 😉)
So with Q4 planning happening next week, now’s the last chance to get your voice heard before we go all Bob the Builder on this thing.
We invite you to drop your thoughts in the thread and let us know what you’d like to see fixed, improved, or expanded on the Railway platform.
As always, we thank you most enthusiastically for your support. 🫡
Better Guides Are Coming
We’ve leveled-up our Community and Developer Relations capabilities by bringing on a talented new Community Engineer (Welcome, Brody!) and a talented new DevRel Engineer (Welcome, Prosper!).
Among many other things, this means that we can start to do a lot more in terms of writing great guides and documentation.
Here’s what’s new so far:
- There’s a new Best Practices guide
- There’s a new Fixing Common Errors guide
- There’s a new guide on Deploying a Fastify App
- There’s a new guide on Deploying a FastAPI App
… and much more is planned.
Since we’d especially like to write things that are interesting to you, if you have opinions on what we should write next, open a feedback thread in Help Station and let us know about it — thank you in advance!
Railway Metal Reminder
Last week we let you know that we’ve opened our first Railway Metal region (us-west2) in Beta.
This is an important milestone for us as we decouple from our upstream cloud provider and gain the capability to offer better, faster, cheaper, more configurable, and more reliable service to our users.
We’re extremely excited about this rollout and we’re ready to add some more workloads.
If you’d like to be an early adopter, all you have to do is head over to your service-level settings, scroll down to Region, and select US West (California, USA) Metal Beta from the menu.
That’s all there is to it.
Let us know how it goes.
And have a great weekend! 🏄
Fixes and Improvements
- We added an
Unsubscribebutton to Help Station threads 🙌 - We added the ability to set variables in the CLI with
railway variables --set - We now alias
railway envtorailway environmentin the CLI - We improved the UX around
railway linkin the CLI. Most importantly, you can now link via the project name instead of requiring an ID