What’s up, what’s up, what’s up? It’s the Railway Changelog here coming to you live from HQ which is… distributed around the globe. 

This is the last product update for a little bit as our team will be gathering together (un-distributed?) next week to prepare some big projects for the quarter. We couldn’t be more excited for what’s coming next on the roadmap. 

Now accepting comments for PR Environments!

We think PR environments in their present state are confusing. This is especially true when working with multi-service projects. Since the base environment setting is buried in each service’s settings, the base environment must be edited for each service independently. Not ideal.

We’re collecting requirements to improve PR environment configuration. In particular, we’re interested in clarifying the way PR environments are created and behave for a project.

Some of the things we’re thinking about include forking and merging base environments, having commit-like behavior when configuration changes are made, introducing changesets to collect events not tied to environment history, and more.

 and please leave a comment if you’d like to weigh-in with your PR Environments needs.

Verification standards are tightening to provide a better experience to legitimate users

We’ve been flooded with spam users for some time. It’s not fun to deal with. In response we’ve tightened verification standards to give legitimate users a better experience on the platform. 

New Railway users will need to provide a GitHub that meets minimum age and activity requirements. Users that are unable to provide a history of legitimate GitHub use will need to add a card to unlock Railway resources. 

We’re making these changes as part of a larger effort to drive the product forward for production users and teams. As part of this effort we’re going to be making some updates to pricing and packaging that we think will clarify the product offering and make it easier to envision scaling on Railway. 

With your help we’ll make Railway the best place possible to deploy your next application. Thanks for your support. 🙂

Note: we are traveling to for our in-person retreat so you may see these updated UI changes rolling out start of next week. 

We finished our migration from Twin Macro to Vanilla Tailwind! We’re writing a blogpost to explain why we did all this — so stay tuned!

We fixed a number of responsive styling issues

https://res.cloudinary.com/railway/image/upload/v1681508988/og-images/changelog-pr-env-verify_t2umry.png

PR Environments RFC, Changes to Verification

Changelog #0129