Want to share your Railway projects? We just made it a lot easier! This week we’re letting you know about Public Projects, editable plugin names, improvements to Ruby support, and more.
Let’s jump into it.
Public Projects
In the past, we launched Public Projects as Templates to allow users to view and run publicly running projects.
Now we’ve added the ability to convert existing projects to Public Projects. This will allow you to share your project with other users without needing to create a new template or invite them to your project.
When changing project visibility, which is now available in Project settings, none of your secrets are exposed to the public.
We’re looking forward to seeing what you share!
Editable Plugin Names
It is now possible to assign a custom name to plugins within the plugin settings pane. Why is this noteworthy? Because this is the first step toward allowing multiple instances of the same type of plugin within a project!
Stay tuned for more news on this front. 😎
Improved Ruby Support
Nixpacks Ruby support has been upgraded and should now take half as long to build and deploy with a cold cache (even faster with a warm cache). The main improvement is using Rbenv rather than RVM to install specific versions of Ruby.
Ruby support is still not perfect. We are continuing to improve the builder’s caching abilities across services and projects.
Feedback and suggestions are always welcome when it comes to improving build performance. Please feel free to jump onto Discord and let us know your thoughts.
Improvements and Fixes
- Nixpacks upgraded to v1.1.1
- Improved the flow to update credit card information
- Improved email communications for delinquent invoices