 we demoed a sneak peak into the new Template Composer that we’ve been working on. We envision this composer as a next-gen or drop-in replacement for the 

, which we’ve found limiting in a variety of ways. 

In short, we’d like you to be able to create templates of arbitrary complexity and to be able to share (and even monetize) those templates very easily. So we needed to build a better system to support the next wave of template creation.

This week, we’re excited to land the Template Composer in your inbox as an opt-in feature flag.

Excellent! The train is just now departing. 

The Template Composer is a new way to build templates on Railway

This is the new Template Composer. It looks similar to the standard project canvas, but it’s actually a powerful tool for creating reproducible Railway projects with a few clicks.

First things first — to enable it, you’ll need to visit your 

As a demonstration, let’s try to recreate the 

We can now use the new composer to specify the component parts to this project (in this case QTY 2 Docker images and QTY 2 GitHub repos) and have them appear nicely in the composer’s canvas grid. 

Here we specify two Docker images and two GitHub repos to make up our template

, and pretty soon we have a live, reproducible template available!

Here’s the end result — a template page with QTY 4 services available to the end user to configure and deploy as they wish. 

Templates are available as usual for consumption by others

Did you notice that we’ve made it a lot easier to assemble templates? That’s the goal. 

If you’re wondering about why we’re investing so heavily into the template creation workflow it’s part of a 

 to build a thriving template economy on Railway — something we’ll continue to have much to say about in the coming weeks and months. 

It’s now possible for Pro users to specify private docker images

By popular request, Pro users are now able to define docker images with private credentials from GitHub, DockerHub, or Quay.io!

To create a service from a private image, simple visit the service settings and tap the 

Pulling private repos is something we’ve wanted to support for some time so we’re excited to get this out the door. 

We’d like to know what else you’d like to see supported around private registries, so please do us a favor and 

 what else we can do to help support your use case.

We’re two weeks away from entering our Q2 2024 planning sprint and we’d love to extend the invite to you to please drop us your most pressing feature requests. 

create or upvote a ticket in the Help Center

, but you’re also free to let us know what’s holding you back on Twitter by pinging us 

We have an enormous amount of stuff coming down the pipe and can’t wait for your continued feedback. 

As always, thanks for riding with us. ✌️

We added support for icons in the template canvas

We added support for emojis as group icons in the canvas

We fixed some date formatting and daylight savings related issues with log timestamps

We added a large number of small quality of life improvements to the 

We fixed an issue where variables names in templates couldn't contain 

We fixed an issue when dragging around nested groups of services in the canvas

https://res.cloudinary.com/railway/image/upload/v1710551311/2024-0315_wysw1f.png

Template Composer, Private Registry Support, Call for Feature Requests

Changelog #0177