Welcome to another edition of the Railway Changelog!

In this episode, we’ll be bringing you early access to some migration resources as we transition from Legacy Plugins to Database Services.

We’ll also be bringing you a new way to deploy directly from a public GitHub repo, a new autocomplete function for Railway variables, and a note about some Network billing adjustments we’ve made to fix a pricing spike that some users experienced this week.

We’ve started rolling out resources to help you migrate from Legacy Plugins to Database Services

If this is the first time you’re hearing about this, the tl;dr is that we’re in the process of deprecating Legacy Plugins in favor of Services with attached Volumes … AKA Database Services.

This new architecture unlocks the ability to deploy ANY database on Railway, so we’re really excited to get this migration in your hands.

 users will soon be able to get started migrating from Legacy Plugins to Database Services with this handy guide: 

Migrating from Legacy Plugins to Database Services

We’ve also created the following templates to help upgrade from the primary legacy Railway database providers:

If you’d prefer to wait to migrate your production data that’s A-OK as we still have a couple weeks before this migration path goes to General Availability.

If you have any questions meanwhile, feel free to jump on 

Now in GA, deploy directly from a public GitHub repo!

 the ability to deploy a public GitHub repo from a URL. 

We’ve had a fantastic response to this feature and we’ve decided to make this feature generally available. 

If you’d like to deploy to Railway directly from a (public) GitHub repo URL, simply pull up the command palette (CMD or ⌘ + K), paste a GitHub URL, and press enter. 

 and paste a public GitHub repo there to try out this new flow.

Railway Variables are now available with autocomplete in the Variables pane within service settings

From the Department of Quality-of-Life Improvements comes a new feature designed to help you reference Railway variables more efficiently.

Introducing autocomplete … for Railway-provided variables! 

 field, you should see Railway-provided variables in addition to your existing variables as autocomplete options.

This should make it easier than ever to reference default variables across services. 

We inadvertently caused a bit of indigestion among some users this week when they looked at their upcoming bill for network egress. We wanted to take a moment to explain what happened to cause a few users to see spikes in upcoming egress costs and let you know what we’re doing to remedy the situation.

We started billing for network egress in 

 of this year. Two weeks ago, we recognized that we were only billing for 2% of egress being charged. When we dug in further, we realized that we were undercounting egress by even more than we thought — to the tune of 58x - 59x! 

Earlier this week, we rolled out a “fix” for this undercounting. This morning (Friday), a number of users flagged that their upcoming bills had “popped” and when we dug-in further, we realized that Legacy Plugins were the culprit because they only have external URLs. 

So we wanted to let you know that today we rolled back the recent change that proliferated this pricing pop. For the next month, we’ll be providing a 100% waiver on Legacy Plugin egress, and next month we’ll provide a 50% waiver for Legacy Plugin egress.

We hope this will allow you ample time to migrate off of Legacy Plugins. Please also keep in mind that if you use an internal network, there will be no charge. 

We apologize to those of you who experienced this surprise on the billing page and thanks for your understanding as we remedy the situation. 

 and let us know if there’s anything else we can do to make your experience on Railway better.

https://res.cloudinary.com/railway/image/upload/v1699049902/db-plugins_iazdtq.png

Plugin Migration PB, GitHub URL GA, Variables Autocomplete, Billing Adjustments

2023-11-03-plugin-migration-priority-boarding

Changelog #0158