fix: deploy script uses user systemd and configurable paths #178
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Competitor
Kind/Documentation
Kind/Enhancement
Kind/Epic
Kind/Feature
Kind/Security
Kind/Story
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Scope/Core
Scope/Cross-Plugin
Scope/Plugin-System
Scope/Single-Plugin
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ultanio/cobot!178
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/deploy-script-paths"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changes
REPO_DIRandSERVICEare now env-configurable (COBOT_REPO_DIR,COBOT_SERVICE) with sane defaultssystemctl --usersince cobot runs as a user service, not a system servicejournalctl --userfor log accessWhy
The deploy script hardcoded
/home/alpha/workspace/cobotand usedsystemctl restart cobot-alpha(system service). Alpha actually runs as a user service (cobot.serviceunder alpha's systemd). The hardcoded path also breaks when the repo location changes.Testing
systemctl --user status cobot.service✅ APPROVED
Clean fix. All changes are correct:
systemctl --user— Alpha runs as a user service, not system. This was a real bug that would have caused deploy failures.journalctl --user— matches the systemctl change.COBOT_REPO_DIRandCOBOT_SERVICEwith sensible defaults. Good for CI flexibility without script edits.cobot— correct for user service (wascobot-alphawhich was the system service name).No issues found. Ready to merge.