We interrupt this regularly scheduled programming to show an important commercial from the Railway team regarding this week’s announcement of cash payouts for template authors.
Please roll the tape.
Let’s get into the details!
Cash Template Payouts Are Here
We’re thrilled to announce the arrival of real-cash-money payouts for template authors as part of the Template Kickback Program.
If you don’t know about the Template Kickback Program, Railway will pay you 25% of whatever we make when any user on the platform deploys your template.
Until today, that 25% was only redeemable for Railway Credits.
Now it’s available to be redeemed for cold, hard, cash.
Nice, right?
Cash withdrawals are available in $100 - $500 increments and are awarded via GitHub Sponsors or Buy Me a Coffee.
Check out the Earnings section of your Account Settings to see your available earnings.
And if you don’t have any templates or template earnings yet (you can check here) — now’s a great time to start earning!
Check out the links below to get started.
Withdrawing $500 via Buy Me a CoffeeGet started with Templates:
- Railway Templates Library
- Template Kickback Program
- How to Create a Template docs
- Template Composer
- Earnings and Withdrawals docs
- Link to your account templates
For feedback on this program, please join the conversation here.
New Template Deploy Flow
There’s a new and improved flow when deploying templates into a projectWhile we’re on the topic of templates, did you know that you can deploy templates directly into your existing project?
That’s right, you can. And now there’s a new-and-improved flow for doing just that.
When adding a template to a project, you’ll now see a single configuration pane (see animation above) that makes it much clearer what’s being added to your project.
In addition, templates are deployed with positional awareness from the Template Composer and for those of you that have Canvas Service Groups toggled in Feature Flags, you’ll also get the template deployed into its own service group.
Join the conversation here.
Runtime V2
Railway has been working on addressing a number of annoying implementation detail abstraction leaks that a number of users have run into when they use Private Networking.
So the arrival of Runtime V2 is perhaps a boring update, but the difference compared to the Legacy runtime is that you no longer have to add sleep(3) to your services. It’s the same OCI-compliant runtime we know and love, just better.
As we type, we’re now rolling out Runtime V2 as our answer to this problem.
From now on, new services will be using Runtime V2. There are no changes to your workflow at all. As with all foundational infrastructure, we have a setting that allows you to return to the previous runtime by selecting “Legacy” in your service settings.
We plan to move over all services to this runtime over the month starting with Trial → Hobby → Pro → Enterprise.
Any hiccups? We welcome your feedback on Runtime V2 here.
Features and Improvements
- Getting too many “build failed” or “deploy crashed” emails from us? We added an option to turn off Ephemeral Environment email alerts in your Account Settings
- We added a way to reduce the height of charts in the new Observability Dashboard
- We improved color consistency of resources in the new Observability Dashboard
- We improved position retention in the new Observability Dashboard
- We fixed an issue where it was possible to add a parent group to a child group in the new Canvas