Oh say can you see, it’s time for Changelog #0193. 

This week we’re bringing you a new handy way to duplicate services, we’re making generally available some improvements to the service deployment panel, and we’re officially shipping a way to eject a service from its upstream repo within a template. 

New: Duplicate a service directly from the dashboard

We added a new and easy way to duplicate a service in the dashboard. 

To get started, all you need to do is right-click a service and select 

Let us know what you like or don’t like about this feature by dropping a comment in the feature thread 

New deployment information panel is now generally available

We’ve been busy making some improvements to the service deployment panel when deploying or redeploying a service. 

In particular, we’ve been working to communicate a more clear history of your deployments and to make it more transparent what stage your currently deployment is in.

We’re also aiming to make it easier to recognize the error or errors that might be interrupting your current deployment. 

So this week we made generally available the first new design for service deployments. 

We hope you find it a bit easier to understand what’s going on with your deployments. 

If you have feedback for us, we’d love to hear it 

Ejecting a service from a template is now generally available

 but you’d like to customize one or more services within the template — previously there hasn’t been an easy way to do this other than forking the repo via GitHub, making changes, deploying from the forked repo, and so forth. 

Now we’ve introduced to general availability an 

 function. This creates a copy of the template service source inside your own GitHub account so you can do whatever you want with it — all within the Railway dashboard. 

It’s as easy as selecting the service within your project, navigating over to settings, and hitting the 

We fixed an issue that sometimes caused errant 404s to show up when using the Railway dashboard

We made improvements to the way we display cost usage breakdown charts at the project level

We added dates of the current billing cycle to usage limit notification emails

https://res.cloudinary.com/railway/image/upload/v1720228676/2024-0705_yato1c.png

Duplicate Services, Improved Deployment Information, Template Service Eject