Have a security-minded coworker that’s new to Railway? 

Well you’re in luck as this week we’re introducing a new Slack Bridge for that. 

That’s right, folks, this week we’re coming in hot with resources to make your experience on Railway as great as possible. 

Without further ado, let’s all please mind the gap and find our seats. 

The new Railway Trust Center is available at trust.railway.app

This web property allows you to review Railway’s compliance posture on such topics as GDPR, SOC 2, and HIPAA.

It also makes it easy to download documents that you might need such as the Acceptable Use Policy, Data Security Policy, and so forth. 

If you’re a Pro team with substantial compliance needs and you’d like to talk to us about SOC 2 or HIPAA, we invite you to schedule a session 

There’s a new easy way to file a help ticket directly from Slack

 user with a direct Slack channel with the Railway team, we’ve enabled a new way to get your questions resolved faster. 

 command in Slack, you’ll first be asked to make sure your Slack is connected to your Railway account via 

Angelo: “You might be wondering how I got here.”

So I was in progress of rolling this feature out until I realized I didn’t test the flows on different Workspaces. See, I worked in a Shared Channel in a Dev workspace, I had two different workspaces connected but since the command was the same I couldn’t tell them apart. Imagine my surprise when I saw no Slash Command.

As such: I didn’t realize I wasn’t able to invoke a command in a shared channel from another workspace. Massive egg on my face.

So I am doing you one better. I did some research. Out of 100+ channels, none of you stop by to say hello. 

You want to talk to us direct because something’s gone horribly wrong. Now immediately when you post a message as a member, we immediately spin up a thread and apply a SLO timer to the support on-call. It only applies to channels with the Railway Support app installed which I am rolling out in stages. No more dropped Slack threads. 

We are so confident in our ability to be responsive to user requests on Slack now that we have also lowered the requirements needed to get a Slack Channel. Want a Shared Slack Channel? 

The new edge proxy is now the default for most services

), we’re rolling out a new edge proxy to speed up deploy cutovers, provide richer error pages, and a whole host of other benefits that are coming down the line. 

As of this week, all new domains are using the new proxy. 

If there’s a reason you need the legacy proxy (unlikely), you can now toggle the legacy proxy in your network service settings.

Over the next month we’ll be transitioning all existing service domains off the legacy proxy and onto the more performant new edge proxy. 

Custom domains will remain configurable for a bit longer than that.

Setting up Proximity Steering Using Cloudflare

 useful for those who want control over routing their app

We made it so that service domain ports are now part of the staged config. This means that if you have multiple ports configured, they'll be respected in PR environments

We finished migrating all templates to the new 

 v2 infrastructure. That means we’re now able to push features and flows around templates faster as we don’t have to manage both systems

We fixed a bug where services would sometimes fail to delete in some cases

We fixed a bug where deployments in PR environments would sometimes be stuck on "Waiting for CI"

We fixed a bug with the template creator not showing up on the template details page

https://res.cloudinary.com/railway/image/upload/v1722647959/2024-08-02_yblcgx.png

Trust Center, New Slack Bridge, Edge Proxy Cutover Progress

Changelog #0197