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.
Restart Deployment
For those in Priority Boarding (to join, type “/beta” in our Discord) 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”.
Support Flow Improvements
Last Changelog, 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.
Railway Local Shell
We’ve added a new command to the Railway CLI: railway shell. This will create a subshell (based on $SHELL) 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 railway run. Thanks for the great suggestion Wyzlle!
Upgrade the Railway CLI to version 1.5.0 to use it!
Improvements and Fixes
- 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.
- Various UI bugs fixed
New Video on Demand
Our globe trotting software engineer Faraz was on Learn With Jason this week. Faraz walked through setting up self-hosted analytics and demonstrating our starters and product. Watch the replay of the stream here!