Build Timeout on Deploy from GitHub Branch
I'm working on a PR for the Chatwoot application that will allow a user to deploy chatwoot to Railway using the "Deploy to Railway" button with a template. I'm testing the branch for the PR now but I'm experiencing a build timeout. Is there any way to increase the build timeout? Here's a link to the branch for the project: https://github.com/lauriejefferson/chatwoot/tree/chore/5344-Support-easy-deployment-on-Heroku-competitors
GitHub
GitHub - lauriejefferson/chatwoot at chore/5344-Support-easy-deploy...
Open-source customer engagement suite, an alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬 - GitHub - lauriejefferson/chatwoot at chore/5344-Support-easy-deployment-on-Heroku-comp...
11 Replies
Project ID:
3b10c352-aef0-402f-bcf7-348d1a1599173b10c352-aef0-402f-bcf7-348d1a159917
hello I'm the maintainer of the current chatwoot template and on behalf of the users I'd ask that you'd please refrain from publishing duplicate templates, it is very confusing being presented with two identical templates when you search for an app
and with that said, is there anything my template is missing that prompted you to try to make another chatwoot template?
oh and for reference, this is the chatwoot template I've made https://railway.app/template/chatwoot
Thank you for you response. I was trying to complete Issue #5344 https://github.com/chatwoot/chatwoot/issues/5344. Since you already have the template, is there a "Deploy to Railway" button on the chatwoot repo?
GitHub
Issues · chatwoot/chatwoot
Open-source customer engagement suite, an alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬 - Issues · chatwoot/chatwoot
the markdown button would be
[](https://railway.app/template/chatwoot)Thanks I will add the markdown button to the PR.
sounds good!
When I tried to deploy a chatwoot project from the template I get a "Repo name collision" error
okay that makes two users who have reported this, thats an issue with railway and ill bring this up to the team
Should be fixed now!
It's working now. Thanks.