ci: deploy every merge to dev2 - #138
Merged
Merged
Conversation
Railway deployed on merge by itself; the box did not. Same workflow as crawlproof.com: ssh to dev2 with a deploy key and run the site's deploy-app.sh at the merged commit, then check /healthz. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
nichedb.dev moved from Railway to dev2 on 2026-09-24; Railway used to deploy on merge and the box did not. Same workflow crawlproof.com uses: ssh to dev2 with a deploy key (repo secrets DEV2_SSH_KEY, DEV2_KNOWN_HOSTS, DEV2_HOST, DEV2_USER, already set) and run the site's deploy-app.sh at the merged commit, then verify /healthz.
🤖 Generated with Claude Code