10 months ago
why it creates docker image of the project every time when there is change in GitHub source, I don't think it is an effective way of applying source file changes, it should be as simple as applying any change to that file , instead it restarts the whole process of creating image from installing requirements to the end.
Pinned Solution
10 months ago
Railway doesn’t just copy your changed file, it rebuilds a Docker image every time so your app runs in a clean reproducible environment. That's how Docker works.
2 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 # Help: Deploy prebuilt Docker image via GitHub Actions without rebuild
- 📚 Quick Start Tutorial
- 🧵 Trigger redeploy after docker image rebuild
If you find the answer from one of these, please let us know by solving the thread!
10 months ago
Railway doesn’t just copy your changed file, it rebuilds a Docker image every time so your app runs in a clean reproducible environment. That's how Docker works.
Status changed to Solved brody • 10 months ago