Repository navigation
ci: deploy every push to main through Carrel - #21
Merged
Merged
Conversation
The release workflow sends a Carrel app release after the image is pushed; carrel-deployd runs deploy/carrel-start.sh, which pins the image tag in .env and waits for a healthy web container. Co-Authored-By: Claude Opus 5.5 <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
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.
Summary
deployjob to the release workflow: after the image is pushed it sends a Carrel app release (winfra/gallery) holdingdeploy/carrel-start.shandVERSION.deploy/carrel-start.shpins the image tag in.env, pulls, runsdocker compose up -d --wait weband reports ready, same as portal.Verify
app_link), carrel-deployd is active on the machine and the unit has theType=notifydrop-in.live.🤖 Generated with Claude Code