Hey, we've changed how templates work. The repo creation step doesn't exist anymore and the template is deployed directly from the source repo.

More here: https://railway.app/changelog/2024-03-01-plugins-deleted#improved-template-deploy-flow

Wait, what? What is the point to do that?

So now I need to fork manually from your https://github.com/railwayapp-templates account and then to clone from Railway?

Wait, what? What is the point to do that?

We noticed that the majority of users using templates would never make any changes to the source and additionally did not want multiple repositories in their own GH account every time they deployed a template.

So now I need to fork manually from your https://github.com/railwayapp-templates account and then to clone from Railway?

For now, that'd be a workaround yes. You could either fork the repo into your account or clone + push but we're open to adding a flow similar to before where you could eject out of the template into your own repo right from the Railway dashboard.

Could you tell me the flow you were using in the past + what your ideal scenario is?

I get that some people do not want to flood their GH accounts with repositories but this new way does not work for a lot of templates. A clear example is the NGINX Sever Template, where you really need to modify it, and right now it is useless since you have no access to the template itself.

I find the other way a lot of more convenience to be honest.

Or at least add the 2 option as you well said:

1) Run the instance from the Template Source Repo (for a minimalist approach)

2) Eject out of the template into your own GH repo (when is needed)

Could you tell me your workflow with this template and what the ideal eject behavior would be? Is your expectation something as simple as hitting eject creates a new repository under your GH account or would you expect something else as well?

My friend, as I said my perfect scenario was as it worked before; it was smart and very convenience.

But flowing this new minimalist approach a simple eject button (to change the Source Repo by creating a new repository under my GH account) it would work for me.

Let me cook something up. W̶i̶l̶l̶ t̶r̶y̶ a̶n̶d̶ h̶a̶v̶e̶ s̶o̶m̶e̶t̶h̶i̶n̶g̶ b̶e̶f̶o̶r̶e̶ t̶h̶e̶ e̶n̶d̶ o̶f̶ t̶h̶i̶s̶ w̶e̶e̶k̶ o̶r̶ e̶a̶r̶l̶y̶ n̶e̶x̶t̶ w̶e̶e̶k̶.

Editing to remove timeline as I have a wisdom tooth situation.

Available behind a feature flag. 👍

https://railway.app/account/feature-flags

Available behind a feature flag. 👍

https://railway.app/account/feature-flags

You are the man. It works perfectly.