2 months ago
Chatwoot application keeps failing in multiple instances even with update from the repo, and this has been going on for months.
2 Replies
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 2 months ago
2 months ago
Hello ambav,
i think based on what i can see, railway's own official chatwoot template no longer uses multirun with both processes in one service. they split it into two separate services , one running bin/rails server -b 0.0.0.0 -p $PORT and one running bundle exec sidekiq, both using the same chatwoot image, both with volume mounted at /app/storage only. you can see the exact setup at railway.com/deploy/self-host-chatwoot , that's the architecture railway themselves recommend now. worth trying since everything else in this thread didn't stick
Hope this help you :)
domehane
Hello **ambav,** i think based on what i can see, railway's own official chatwoot template no longer uses multirun with both processes in one service. they split it into two separate services , one running `bin/rails server -b 0.0.0.0 -p $PORT` and one running `bundle exec sidekiq`, both using the same chatwoot image, both with volume mounted at `/app/storage` only. you can see the exact setup at [railway.com/deploy/self-host-chatwoot](http://railway.com/deploy/self-host-chatwoot) , that's the architecture railway themselves recommend now. worth trying since everything else in this thread didn't stick Hope this help you :)
2 months ago
Ok, I'll try and send feedback
