--- title: "Template Composer, Private Registry Support, Call for Feature Requests" date: 2024-03-15 number: 0177 url: https://railway.com/changelog/2024-03-15-template-composer --- # Template Composer, Private Registry Support, Call for Feature Requests [Three weeks ago](https://railway.app/changelog/2024-02-16-private-threads#sneak-peak-template-composer) 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 [legacy button workflow](http://railway.app/button), 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. Would you like to see it? Excellent! The train is just now departing. Please mind the gap. ## New Template Composer [Image: 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 [feature flags](https://railway.app/account/feature-flags) page and toggle `Template Composer (Alpha)`. As a demonstration, let’s try to recreate the [OpenTelemetry Collector Template](https://docs.railway.app/tutorials/deploy-an-otel-collector-stack) that Melissa shipped last week. 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. This is what it that looks like: [Image: Here we specify two Docker images and two GitHub repos to make up our template] Next we’ll hit `Create 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. Nice! [Image: 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 [larger effort](https://railway.app/changelog/2024-03-08-credit-transfers#credit-transfers) to build a thriving template economy on Railway — something we’ll continue to have much to say about in the coming weeks and months. Pretty cool! We hope you like it. ## Private Registries [Video: 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 `Add Credentials` button under the `Registry Credentials` heading. 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 [let us know](https://help.railway.app/) what else we can do to help support your use case. Thanks! ## Call for Feature Requests 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. The best way to reach us is to [create or upvote a ticket in the Help Center](https://help.railway.app/feedback), but you’re also free to let us know what’s holding you back on Twitter by pinging us [@Railway](https://twitter.com/Railway). 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. ✌️ ## Fixes and Improvements - We updated our [Terms of Service](https://railway.app/legal/terms) and [Privacy Policy](https://railway.app/legal/privacy) - 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 [Help Station](https://help.railway.app/) - We fixed an issue where variables names in templates couldn't contain `.` in them. Variable names like [`user.name`](http://user.name/) are now acceptable - We fixed an issue when dragging around nested groups of services in the canvas