Feedback time!! -

• You would need to use a logo with a 1:1 aspect ratio

• The thirdweb service is missing an icon

• The thirdweb service does not have a health check

• The thirdweb service does not have descriptions of its variables

And if I'm being really nit-picky, the overview could do with a little more content, with a nice header logo like you have here - https://github.com/thirdweb-dev

You would need to use a logo with a 1:1 aspect ratio

Sorry for the image, didn't expect to crop like that. XD Will update it.

The thirdweb service is missing an icon

Oh, I see, will do.

The thirdweb service does not have a health check

Working with the team to get the exact path.

The thirdweb service does not have descriptions of its variables

Thanks, will update it too.

https://github.com/thirdweb-dev

I might use this as the logo, but I think I'll get the official hosted logo.

Wait, the description supports markdown image?

Yeah, markdown and HTML, though compatibility is not as good as GitHub's markdown renderer.

How about this for the logo? https://lw3-teams-logos.s3.us-east-2.amazonaws.com/thirdweb-team-logo?.png

That works! I updated the description will add more just getting some info from the team.

Add a border radius to the header image to appease the perfectionist in me :)

Added the health check, will update the variables description.

For the border radius that would be HTML+CSS! haha will do

Yeah just some simple HTML+CSS

I will see about asking the team if I am allowed to unpublish the failing and unmaintained template in favor of your official template, but no promises since Railway doesn't yet have any policies in place for this kind of thing.

No worries, we wanna make sure that people have alternative options to deploy the template and make sure that it is working.

From first hand experience duplicate templates are not wanted, but the current situation definitely warrants it.

Hey Brody!

All done

• Updated variables description.

• Border-radius for the banner.

• Service icon added for thirdweb.

It looks great, Thank you so much for this awesome template!

Hey Brody!

Done, finalized even the description.
We're going to update the read me with the deploy badge.

Oh wow that looks even better!!

Will publish today a guide how to deploy on Railway with the template. 🤙

Should be a short guide, Railway makes it quite easy to deploy a template eh?

Yes, agree! It should be short and simple. 💫

Link that here when you finish it!

I can update my original template. It was working fine originally with its connection to Prisma so I guess there was a change b

I think it would be best for everyone if a thirdweb developer holds the only thirdweb template, we don't want duplicate templates as that significantly lowers the developer experience, I ask that you please unpublish your template, thank you so much for understanding!

I took the initiative to create the template and update it in the first place. My motivation was to create the template to provide value to others while also benefitting from the 25% usage kickback. Why should I not get that kickback anymore because Thirdweb has showed up? I would like to remind Thirdweb that I created the template and added the template to the thirdweb readme. I would also like to remind thirdweb that they got me to remove my referral code from the thirdweb readme and that thirdweb didnt know about railway templates until I made the PR. Does not seem fair in the slightest that my template is not to be used anymore.

Hello, @thevolcanomanishere. I understand how you feel, and we want to ensure the template is healthy, well-maintained, and updated. However, the original template is in bad status, affecting our developer experience. This can cause an increase in our support ticket, given that this is beyond our support, as we don't have access to the template to update it or fix any issues. I hope you understand.

I'm willing to unpublish our version to support your initiatives; we appreciate your effort. Kindly ensure that the template works for everyone and keeps its status healthy, as per Brody. After we unpublished it, we recommend adding "Unofficial" somewhere to your template; this will help the users understand that this is beyond our support.

Link that here when you finish it!

Thanks, Brody, for all the help earlier; we may publish a different template soon instead.
I'm currently writing a draft for the guide but unfortunately I decided to drop it.

thevolcanomanishere, I share the same thoughts as waren here but my prospective is from the Railway side of things,
when someone comes to Railway for the very first time and their experience was with a broken template that is a horrible experience from a user perspective, and it is damaging to Railways image of simplicity.

Your template hasn't worked for ~20 days, but waren has been extremely attentive to this process and the community, even having tried to reach out to you but was left unanswered, they have shown that they are able to provide fast support for deploying thirdweb onto Railway.

I can understand you may not want to unpublish, and I can't make you, but I would be extremely appreciative if you would consider letting waren have the thirdweb template, again thank you for understanding.

The first email I got about there being a problem, 13 hours ago. I did not get any notifications about my template failing either. The template has worked fine since I created it. There has since been updates to the repo that must have caused the errors. I have since updated the repo and everything is working.

I am going to delete my template so Waren can take this over.

I am pissed off at thirdweb and railways response here. What is the point in someone like me going to this effort only to be told to delete it so that a company like thirdweb gets to replace what I did and then benefit from it?

I definitely understand how you feel, and while Railway doesn't send out notifications for failed template deployments as that would be impractical for the most part at this time, the success score is still available to view at any time provided there is enough data to generate a score, and there was, so you would have been able to see the score plummeting for quite some time now.

Thank you for offering to unpublish your template, that is extremely appreciated!

I think I can speak for both of us here when I say that we are very grateful that you took the time to create your template in the first place, but ultimately I believe that the owner of the template should be someone who is attentive to the community and the health of the template, and in this case that also happens to be a developer for the service the template deploys, as that is highly beneficial to both the Railway and thirdweb communities. I can't thank you enough for your understanding here.

Hey Brody,

I have an update about the template tutorial; we released this today.

• How to deploy your self-hosted thirdweb Engine on the Railway

I added this to the template description as well.

Awesome tutorial!

Thanks, I will release another tutorial about it by tomorrow and we'll promote it on our socials (hopefully a video tutorial as well).

Our train Engine found its own Railway track. 🚂🛤️

Thank you again for picking this up and creating a great template!

Hey Brody, here's the complete guide!
https://blog.warengonzaga.com/how-to-deploy-a-self-hosted-thirdweb-engine-on-railway-in-less-than-3-minutes

Hey Brody, do you know why the health is not 100%?

There's a few things that are out of your control that can cause a lower success score, for example -

• One of your services may use more resources than what a trial plan allows for, crashes due to OOM unfortunately count towards the score, same with crashing due to out of disk space, not ideal and I'm sure that will be improved in the future.

• It could be a user error, the user may not fill out the variables correctly causing the app to crash that will also count towards the score.

The score is currently calculated dynamically every day based on the last 25 deployments, in all honesty it's very rudimentary and by no means a perfect metric, the team is looking for ways to improve the visibility of template health, so please do share any ideas you have on that topic!

And thank you again for being so attentive with your template, that means a lot to me.

Hey Brody, thank you for your update and for sharing information about the health of the template.

I tried it yesterday to test the deployment and can see no problem with the deployment. I was worried something was broken in the template, so I immediately tested it to see what was wrong. However, I couldn't figure it out and posted it here. I'm monitoring the template weekly and working closely with our Engine engineer for any new updates so I can apply it immediately to the template.

Is there any way I can receive a notification if there's a problem with the template? I can only receive notifications here on this discussion page.

At the moment the only observability would be the score that's updated daily, there's no way to do notifications on deployment failures, Railway would first need to sort out a way to gather sanitised metrics in order for notifications to be of much use, but rest assured they will improve the template health observability for both the creators and the end users in due time!

Glad to hear the update Brody, for now I'll check here from time to time.

Happy to help!

Hey folks, we updated the template. This time, we added Redis!

If you use the existing template, follow the instructions to update your engine to v1.0.0

• Open your project and add a new service called "Redis."

• Close that, open your Engine service, and add a new variable called REDIS_URL with a value of ${{Redis.REDIS_PRIVATE_URL}}?family=0 and then redeploy it.

You should be using the latest engine image after you redeploy it.

For any questions, please let me know.

It would be best if you could use the private URL for this as to not expose the template users to egress fees for redis.

I tried it Brody, however I'm getting connection issues with Redis can you try?

Do you use ioredis internally? if so, append ?family=0 to the redis url.

I use the redis from bitnami with the latest version image, is that ioredis?

Looks like appending with ?family=0 to the Redis private URL works.

I updated the instruction above.

Awesome, but for clarity I was referring to the redis client that thirdweb uses internally, nothing about Railway.

I see, basically one of the new requirements for the engine is by adding Redis to the installation.

Template looks good, you just need to correct your start command to remove the redis url parameter for nc since that's not valid syntax for the nc command.

Alright let me try that.

Hey Warren, looks like a Debian based image is now used, thus your custom start command with nc does not work anymore because nc is not installed by default on Debian.

Hey Brody,

How to fix this? Do we need to install it first via command then run the start command? Any recommendations?

No you wouldn't want to install an apt package in a start command, that would delay the starting of the app significantly, it needs to be installed by the Dockerfile.

In the meantime it may be best to remove nc from the start command.

I see, let me figure that out and let you know. I think dockerfile can manage to do that.

I updated the template and removed the NC command to start the service.

Thanks!

You may not even need the nc command anymore, with the v2 runtime now default for new deployments there is no delays in the availability of the private network, and if postgres or redis doesn't deploy before thirdweb, thirdweb will crash and try again up to 10 times.

TL;DR don't worry about adding nc back.

Yeah, actually I tried it, and I'm surprised that it is working normal and I can see that the mysql and the reddis finished to deploy first before the engine. I think removing the NC command should be fine.

Railway now has all around faster deploys.

Indeed, I noticed it and just one click I have the Engine running within 3-5mins.

I noticed the health status is going down Brody? Any idea why?

REMINDER: For existing template users, please remove the start command from your Engine service settings and redeploy the engine if you want to use the latest version. Also please keep in mind that the newest version of Engine from v1 requires REDIS service. For any questions or need further assistance please let me know or send us a ticket here: https://thirdweb.com/support thanks!

Hi, liked the template a lot. Can I get the template code? I would like to learn more and contribute.

Hey there, are you referring to the actual Engine code or how the template itself? Because if the template itself there's no code to it.

Hey people here!

If you folks want to upgrade to v2.0.0 of Engine all you have to do is to redeploy the Engine instance and you are good to go.

For any issues or problems feel free to message here or submit a ticket directly to our support page. https://thirdweb.com/support

Also to add it Brody, I can see that the template is now in 100% health I'm happy to see it now.

I want to add here, I updated the guide from my blog how to update your Engine.

https://blog.warengonzaga.com/how-to-deploy-a-self-hosted-thirdweb-engine-on-railway-in-less-than-3-minutes#heading-update

Here's an update regarding Engine!

Your engine will have now a way to notify you.

https://blog.thirdweb.com/changelog/engine-alert-notifications/

Hey Brod,

Do you have idea why the health is dropping? It is now 80%

Likely users who are deploying it incorrectly, not specifying the correct api keys or similar.