April is grease month and the team is working on foundational improvements to the platform. This means that most of the major user facing features should rear their heads out a little bit later.

For those in Priority Boarding (to join, type “/beta” in our 

) we have rolled out the deployment restart feature. This is useful when you want to restart an application that may not crash but rely on a connection to an external service on initialization. 

To use it, click into a deploy, in the logs view open the Command-Palette, then type: “restart”.

, we announced a number of improvements to the Discord community that made it easier for users to get help with their projects. 

One of our server conductors extended this further. Members can now close their own support threads, be notified if the issue they are facing that might be related to an on-going incident, and made it all around easier to ask your questions. 

We’ve added a new command to the Railway CLI: 

) with all the variables from your project/environment/service loaded and accessible. This can be super convenient if you want to run a bunch of commands and don’t want to prefix them with 

Fixed an issue with the New Project creation flow

Scaled up more of the underlying infra to meet demand

Discord bot developers rejoice! We have lowered the instance count on each box. Hopefully solving rate limit issues.

 this week. Faraz walked through setting up self-hosted analytics and demonstrating our starters and product.

https://res.cloudinary.com/railway/image/upload/v1650671660/docs/railway-local-shell_ys60cc.png

Restart Deployment, Support Flow Improvements, Railway Local Shell

Changelog #0078