Bug in creating template from existing repository

2 years ago

It looks like when you click the "Generate Template from Project" it includes your database services in the standard "services" list.

This causes issues when you try and deploy. The template form wants you to fill out all the environment variables and these should all be automatically created by railway as part of your database spinup.

Is there a way you can remove a service from your template? or am I going to have to remake this from scratch?

10 Replies

2 years ago

N/A


2 years ago

title should read "Bug in creating template from existing project"


2 years ago

you can't remove services from templates, also not quite a bug because this is technically intended behaviour


2 years ago

Hmm okay. Do you see the issue regardless though?

Effectively, if you have a database service you can't use that "generate a template from this project" button because the database service will be pulled in as a service.


2 years ago

I see how technically this isn't a bug because databases are just services with volumes + some extra UI in the dashboard now, but it's definitely subpar UX.


2 years ago

yes i do see how it poses an issue, the solution being of course to remove the database from the project before you create a template from it.

both these issues will be fixed with the v2 template composer https://railway.app/changelog/2024-02-16-private-threads#sneak-peak-template-composer


2 years ago

Good to know!


2 years ago

ended up getting the template up and published 👍
https://railway.app/template/kwu__Y


2 years ago

I saw, I left some feedback on its forum post for you


2 years ago

Thank you! I'll check that out.


Loading...