Repository navigation
feat(systemd): the units answer to recasaos* names too - #26
Merged
Merged
Conversation
Alias=recasaos*.service in [Install], so `systemctl restart recasaos` works while everything that uses the casaos* names keeps working. The setup script already runs `systemctl enable --force` on every install and update, and enable adds a new Alias to a unit that was enabled before, so existing boxes get the names on their next update.
This was referenced Nov 5, 2026
inkly
approved these changes
Nov 6, 2026
inkly
left a comment
inkly
left a comment
Collaborator
There was a problem hiding this comment.
Looks good. I checked the part that matters for existing boxes: the setup scripts run systemctl enable --force on every install and update, so the alias appears without a reenable step, and the uninstaller's systemctl disable removes it again. Thanks!
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.
Alias=recasaos….servicein[Install]ofcasaos-local-storage-first.service,casaos-local-storage.service, sosystemctl status recasaos…andsystemctl restart recasaos…work, while everything that uses thecasaos*names keeps working. Part of the service names question in ReCasaOS/CasaOS#84. The other units: ReCasaOS/CasaOS#95, ReCasaOS/CasaOS-Gateway#7, ReCasaOS/CasaOS-MessageBus#10, ReCasaOS/CasaOS-UserService#10, ReCasaOS/CasaOS-AppManagement#41.Existing boxes get the names on their next update, without a
reenablestep. An alias exists once the unit is enabled. The setup script already runssystemctl enable --forceon every install and update,install.shcopies the new unit files before it runs the setup scripts, and the update button runsinstall.shtoo.systemctl enableon a unit that is already enabled adds anAlias=it did not have. I checked this on a Linux Mint 22.2 box (systemd 255) with a test unit, without adaemon-reloadin between as well.Tested on that box (v0.5.84): I put the unit files of the PRs in place and ran the same
systemctl enablethe setup scripts run. Everyrecasaos*name resolved to itscasaos*unit (systemctl show -p Id) and was active,systemctl restart recasaos-gatewayworked, and after a reboot all were active.systemd-analyze verifyis clean.systemctl disable, which the uninstaller and the cleanup scripts run, removes the alias symlinks too.One thing the alias does not do:
journalctl -u recasaosfinds nothing, because the journal keys on the unit's real name. Logs stay underjournalctl -u casaos.