Welcome, Passengers, to another edition of the Railway changelog!

This week we’ll be taking you through some improvements to the edge network and letting you know about a couple of big upcoming projects, including the beginnings of RBAC on Railway and our progress towards Railway Metal (our own datacenters). 

We also squashed a large number of bugs and polish items which you can find at the end of the doc. 

If you’d like to see more nits squashed, it’s not too late to get involved in 

Also — as another programming note, we wanted to let you know that if you applied previously to 

, we should have responses out to you soon. (Thanks again for your interest!)

This week we made a few improvements to the proxy:

We now enforce a minimum of TLS 1.2 to mitigate downgrade attacks from less secure versions of TLS.

You can now use any encoding you’d like as long as your application supports it. Whatever the downstream client passes in the 

 header is exactly what your application will see and it's then up to your app to handle this. (Although we previously handled this for you, we felt it was more flexible to have your apps handle this negotiation so you can support any encoding you want.)

 header to track diagnostic information to requests on the new edge network. (Note this was previously known as 

 but we changed the header name since it conflicted with other HTTP API services.)

We’re excited early next week to start rolling out 

These will be variables that you can obscure for security reasons — extremely useful and necessary depending on your team collaboration needs. 

For a little bit of perspective, this marks the beginning of Railway’s RBAC (role-based access control) story. While we’re starting with variables, this will be expanding over time to satisfy tiers of access control needed for many production teams.

We couldn’t be more excited to ship the features your team needs. If there’s a feature blocking your company from succeeding on Railway today, please 

Meanwhile, please stay tuned next week for this feature dropping. 

Railway Metal is coming soon and we couldn’t be more excited

t’s been a while since we last updated you on our plans to light-up physical Railway servers, but we now have our first workloads running on metal and hope to roll these out for users in the coming weeks. 

Deleting our most problematic upstream dependencies

Tighter control of hardware configuration to deliver you a better Railway experience

As always, if you’d like to help us build this out, 

 and along the way added default support for PNPM 9. We also now correctly stream PHP-FPM output to logs and auto-detect cairo libraries

We improved Help Center notification emails to provide useful context and pull quotes when someone responds to a thread 

We improved the volume migration workflow by patching a bug that was causing a memory leak during the migration process

 for a service after the service is deployed

We fixed a bug where we were showing undefined instead of the URL in the database connect tab

We fixed a bug where users were able to deploy templates without fully configuring them

We fixed a bug where markdown wouldn’t render properly in the variable description when deploying a template within an existing project

https://res.cloudinary.com/railway/image/upload/v1725668322/2024-09-06_m3ctzn.png

Edge Network Improvements, RBAC Is Coming, Railway Metal Update

Changelog #0202