hey, it looks like you have two duplicates for a template that already exists, I would like to politely ask you to unpublish them, duplicate temples create confusion for users who are just looking for a simple deployment option.

Hi brody,

I am the official maintainer of Soketi. The previous one was marked as Deprecated and the new one is the official one.

I'm sorry I had no clue, in that case, I would still like to ask you to unpublish both templates, as one doesn't deploy, and the one just posted deploys from a github repo, that's rather undesirable.

and with those two templates being unpublished, I would be more than happy to get my template transferred to you, as it follows all the best practices for creating a Railway template.

and the one just posted deploys from a github repo

Curious why this is a drawback now that new repositories won't be created for GH based templates?

I would still consider it a drawback on account of it simply not needing to be deployed from a github repo.

I would still consider it a drawback on account of it simply not needing to be deployed from a github repo.

Why?

there's really no deep reason tbh, just doesn't need to be a github repo when the repo contains a dockerfile with a single line and a generic readme.. idk.. feels cleaner? more professional?

[…]
and with those two templates being unpublished, I would be more than happy to get my template transferred to you, as it follows all the best practices for creating a Railway template.

I think I have inquired via mail both Railway and even published a PR a long time ago on your repo, without any answer in both cases.

I would be happy to be having it transferred, if possible.

I'm not sure about the best practices — I see that your repo is still having a Dockerfile with regard to Git deployments.

my template does not deploy from a repo, it deploys directly from your image on quay.io, and fun fact making this template deploy from a docker image is one of the reasons I asked railway to support deploying images from quay.io!

if you would unpublish your two templates, I would definitely be down to get my template transferred to you, you would definitely be the rightful owner.

my template does not deploy from a repo, it deploys directly from your image on quay.io, and fun fact making this template deploy from a docker image is one of the reasons I asked railway to support deploying images from quay.io!

Oh, now it makes sense. Apologies!

for reference, this is the template: https://railway.app/template/soketi

it's missing the Redis database like yours has, and tbh I don't know the importance of it, but if you think it would be helpful to have a redis database in the template and hooked up to soketi, I can make that happen for you before the handover.

My two cents, with the forking change, I'd prefer repos especially if the linked repo contains the source code as I've seen users quite confused with Docker images as they can't see the source.

Other reasons in favor of repos would be:

1. You don't need to know Docker. While you don't need to know it to use images either, it can be a mental blocker.

2. Using repos gives you the option to fork/extend + encourages contributing back to main.

That said, in scenarios like this one where the repo is simply a Dockerfile with a FROM, favoring images makes sense.

in my experience, I've seen a lot of broken templates because they deployed from github repos of source code, as opposed to deploying from images where it's more or less going to work.

I too have seen that confusion but only on templates that used an image where you actually might want to modify something about it.

I personally don't think the kind of person who would be inclined to contribute back to main would be the kind of person who would let a docker image as the source block them.

I'd advise of transferring the template or deprecating it.

I would be happy to transfer it, but I have noticed you still had your template published so I have held off on getting it transferred.

I don't seem to understand this criteria for transferring.

what is left unclear?