Hey there!

You can improve your Build and Deployment times a few main ways:

1. Reduce your container size. The resulting container from your build needs to be packaged up, uploaded to Railway's registry, and then downloaded on your deploying workload. Any space you can save can decrease the times for each of these processes. You may want to look at your package manager and see what dependencies you can remove, or look at your Dockerfile and see if you can use a smaller, more production-ready base image.

2. Reduce your Resource Limits. If you're using replicas, Railway's orchestrator has to find space for the number of replicas * the Resource Limits you have set on the Settings tab. Lowering these limits to a more realistic size for your workload can decrease the time it takes for the orchestrator to schedule your workload.

Tried it 3 times build never completes

Hmm all appears well on my end. Are you still having these issues? Roughly how long was it building for?

more than 10min. it never deployed. So now i've duplicated the service and trying again.

Sounds good! For large apps having 10-15m builds isnt crazy unheard of. Historically what have you seen?

it was always less than 2 minutes so jumping it 10+ in few commits is unreasonable. Also after that long on waiting deployment never completed I tried several times and duplicated the server eventually.

On duplication now it is working:



So really build time is not 10+ minute for this app, there was some issue with old one that was preventing it from deploying.

Hey there!

I noticed you're using our new Metal Build Environment beta -- there was a minor issue with the rollout of a new builder around the time you encountered this issue. That issue is now resolved. Just wanted to let you know!

thanks