Hello, it’s your friendly neighborhood changelog farmer here to bring you news from the harvest.

This week much of the team was lifting some large features into place. As a result, we have one new feature and two upcoming announcements so you have a sense of what’s coming up next. 

You can now set logs to fullscreen in the Log Preferences panel

We know it’s a constant struggle to make sense of your logs when you’re working on a project. Especially when the logs themselves are horizontally … lengthy. 

Now logs can use up all your free screen real estate! 

(And your name doesn’t even need to be Jim Boonie.)

To enable fullscreen, all you need to do is click Log Preferences and select 

. Through the awesome power of CSS, your logs can now bend space and time on your very own screen.

While we’re on the topic of logs, we wanted to let you know that Railway Engineer Greg is working on migrating all of our logs infrastructure over to ClickHouse. It’s going to be fast and wonderful. We’ll holler when that ships.

The Railway billing cycle currently starts at the beginning of every month. If you’re an existing Railway customer, you probably know that you get a Stripe notification email a few days before that each billing cycle.

Why is this bad? Well, for starters it doesn’t make sense to get billed at the beginning of the calendar month if you started your plan midway through a month. It’s also bad because our support queue gets DDoSed at the beginning of every month which makes it difficult to support you all.

We’re making some improvements to billing to help:

Starting June 1st, new Railway customers will have their usage and billing cycle tied to the day they start paying for Railway. Subscribe to the Teams plan on the 10th? We’ll bill you on the 10th of each month. 

One more thing: We’ve heard feedback from some Teams who’d like more alerting around invoice resolution. We have a PR in-flight just for this, and as you might know, billing items take some time to test before shipping to prod. We don’t wanna earn the 

Nixpacks is an important part of Railway and our infrastructure partners who contribute to the project every day. Lead maintainer JR has an RFC that talks about the future of Nixpacks and the coming work that we have planned for the future of the project.

You can read and respond to the Nixpacks RFC 

We want take this moment to thank everyone who has helped with language support on a number of different providers such as Clojure, Haskell, Rust, Ruby, and especially … COBOL. 

Railway relies on our community for so much and we take delight in every PR we review. Those 1.6K+ GitHub stars truly belong to you.

We added logs when a deployment is queued

We fixed an issue with scroll snapping in logs

We made a number of small CSS fixes to the dashboard

We continue to retool our support ticketing system and email cases are now accurately tagged based on the content of the email. 

 Support response times now are under 12 hours on average. We hope telling you this doesn’t jinx our improvements

Our builders now use MASSIVE and FASTER disks. Fewer build errors should occur

https://res.cloudinary.com/railway/image/upload/v1683928953/og-images/cl-fullscreen-logs_l2t2ru.png

Fullscreen Logs, Relative Billing, Nixpacks 2.0 RFC

Changelog #0133