Welcome to another installment of the changelog. 

This collector’s edition is stamped #0185 and it’s in mint condition. 

This week we’ll be taking you on a journey through our internal (non-core) infrastructure, some updates to how Railway writes to your GitHub, and we’ll be introducing a new help feature called Priority Threads. 

But before we get to that, two quick announcements:

There’s still time to apply to the first cohort of the 

 ($5,000 in free credits) — make sure to read the criteria before applying

 — reach out if you’re interested in solving complex problems at the intersection of distributed systems engineering and interface design

Let’s get on with our regularly scheduled programming.

Railway Station is a public project that powers the majority of our non-core application experiences

,” an in-depth look at the public project that powers our forum, docs, blog, and various other production services. 

We open-sourced nearly the entire project, infrastructure and all

We depend on this project to serve hundreds of thousands of users

We’re getting closer to the “ultimate” production demo application

We did this because we want you to explore the production services — running on Railway — that we use everyday. You can check out the project 

And if you didn’t get a chance to read the writeup yet, we recommend you 

Railway now writes human-friendly messages to your GitHub status feed with handy links back to Railway

Next up, we’ve made some improvements to the railway-app bot in GitHub. 

The bot now comments with a list of services and statuses 

The comments now link back to the relevant Railway deployment

Latest deployments are now listed in the root of the GitHub project

There’s direct linking to Railway deployment logs

We’re using GitHub’s native deployment/environments feature to get this done. 

A few months back we shipped “Private Threads.” As the name would imply, this feature allowed Pro users to create private threads.

However, while these threads had a higher precedence internally, we noticed often that many of these issues COULD have been addressed by the broader community.

So, instead of forcing Pro users to decide, we built the best of both worlds — a way to post publicly while maintaining this prioritization internally.

We think this is going to give our Pro users the fastest possible resolutions, while also allowing us to consolidate discussion points publicly.

A screenshot of our redesigned help panel that we rolled out to all users.

We added a link to the relevant GitHub PR in the environment selector for 

 would not always delete when deleting a project 

We fixed a bug where log pagination was using the wrong date when loading more logs in the "down" direction

 charts to make it easier to read in most cases

https://res.cloudinary.com/railway/image/upload/v1715383150/2024-0510_x40pba.png

Railway Station, Native GitHub Deployments, and Priority Threads

Changelog #0185