Hey there! We've found the following might help you get unblocked faster:

• 🧵 TurboRepo deployment: railway up works, GitHub deployment fails with "No projects matched the filters"

• 🧵 Build consistently failing with stale file error after code fix (Node/pnpm/Vite)

• 📚 Deploying a Monorepo

• 🧵 Deploy Service In Shared Monorepo

If you find the answer from one of these, please let us know by solving the thread!

Hey, you probably want to configure watch paths for your services as they are deployed form a monorepo, so that a new deployment is only triggered when the specified paths are changed, documentation regarding this can be found here.

Hey udaian, I've built something similar in the past. An alternative recommendation to uxuz is that you configure your GitHub Actions workflow so that it's triggered on release. You can implement the above option as well, this could then act as a staging environment so as you scale you're able to perform any specific user or feature test ahead of release.

Check out the workflow below:
https://github.com/euanwm/OpenWeightlifting/blob/development/.github/workflows/deploy_prod.yml

@euanwm thanks for sharing - I can try something like this.

@uxuz even if I've configured the path it does not provide me the ability to deploy on demand. That is I want deployment to not happen even iff the path match files were changed. I want to deploy only when I'm ready to ship changes to the customers.

Hey, I would suggest you to use branches. Railway rolls out a new deployment on commit of the specified branch. In this case, you would develop all the new changes on another branch and merge it into main when you need it to trigger a new deployment with all the changes.

Hey, did you manage to find a solution to only manually deploy on Railway?