feat: support service type without repo or build#29
Merged
Conversation
…uild
Allow service instances backed by pre-installed system binaries (e.g.
mailhog) to be managed without a git repository or build step. Only
ssh_host and exec_start are required in deploy.yml.
configure: skip cloning and mkdir the instance dir when no repo_url;
make build optional (run when present, skip when absent)
update: skip git pull and build, go straight to service restart
status: skip git commands and omit Remote/Branch from output
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
6f8d1a1 to
a9a0abf
Compare
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
Adds support for deploying simple system-binary services (e.g. mailhog) as systemd user units without any git repository or build step. Previously,
configurerequired arepo_urlandservicetype required abuildcommand;updateandstatuswould crash on such instances.Minimal config that now works:
configure— whentype: serviceand norepo_url:WorkingDirectory)buildis now optional; runs when present, silently skipped when absentupdate— whentype: serviceand norepo_url:systemctl --user restartstatus— when norepo_urlin config:Remote/Branchlines from outputExisting
serviceinstances withrepo_url+buildare unaffected.Test plan
configureon a no-repo service creates the unit and starts itupdateon a no-repo service restarts the unit without git errorsstatuson a no-repo service showsInstanceandUnitlines only28 passed)