-
Notifications
You must be signed in to change notification settings - Fork 8
setup railway deploy #388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setup railway deploy #388
Conversation
0177e90
to
91e66b7
Compare
91e66b7
to
9a72199
Compare
9a72199
to
3375519
Compare
3375519
to
c0f9828
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR migrates deployment infrastructure from Fly.io to Railway by replacing the existing Fly deployment workflow with a new Railway deployment configuration.
- Removes the existing Fly.io deployment workflow
- Adds a new Railway deployment workflow with Docker build cache optimization
- Configures deployment to trigger on pushes to the main branch
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
File | Description |
---|---|
.github/workflows/fly-deploy.yml | Removes the existing Fly.io deployment workflow |
.github/workflows/railway-deploy.yml | Adds new Railway deployment workflow with service configuration |
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.