This week the team worked on a lot of behind-the-scenes stuff, so this Changelog is on the lighter side. Here are few of the changes that you 

The Railway helpers (and Percy) are a core part of our Discord server and provide invaluable support to our users. This week one of our helpers Neb added an experimental feature to Percy: help thread modals!

 and you will be prompted to fill out a small form with info about your problem. This will hopefully streamline our server and make it even easier for helpers to diagnose issues.

Note that this is still experimental while we test the waters with a Discord.js 14 beta feature.

 we switched the default Railway builder from Heroku to Paketo. Today we reverted that change back to the Heroku builder, which will be the default for 

While we did test the Paketo buildpacks before switching, there were a few common cases that are not handled elegantly. We noticed an increased number of support issues related to buildpacks that would not have been an issue with the Heroku buildpacks, so we’ve taken note of  these and are working with the Paketo maintainers to improve the buildpacks for everyone. However, we felt it necessary to revert back to the old buildpacks in the meantime in order to improve the experience for new users on the platform.

You can still use the Paketo buildpacks by disabling “Legacy Builder” in service settings.

We published a new blog post on how to create and deploy multi-service templates.

https://blog.railway.app/p/multi-service-templates

Fixed the longest-standing typo in Railway. s/charable/chargeable.

Fix error when anonymous users created a plugin from 

Ignore deleted services when creating a template from an existing project

Prevent new service creation unless project has been upgraded to metro

https://res.cloudinary.com/railway/image/upload/v1647035289/og-images/discord-help-modal_pxc5u1.png

Discord Help Modal, Buildpack Woes, and Multi-service Blog Post

Changelog #0072