Change Log¶

v0.6.0 (unreleased)¶

list has a HEALTH column that shows ● failed for units systemd reports failed and ● healthy otherwise.
list shows installed timers in a second table with when each last fired and how the run it started ended.
list no longer shows the SOURCE column unless --verbose is passed.

Added the stop command, which stops every installed project unit, or the named ones, in a single systemctl transaction.

Added the SYSTEMD_SOURCE_DIR setting, a default for install --source so installs use pre-rendered units without the option.

Added the SYSTEMD_RENDER_DIR setting to change the default render output directory from the current directory.
list prints its table with Rich. Output that is not a terminal is never wrapped, so piped rows keep one unit per line.

System scope is now the default: units are managed with the system manager, installed under /etc/systemd/system, and run as the User= they name. The user scope remains available through SYSTEMD_SCOPE or --scope user.
Privilege escalation is explicit and never guessed. SYSTEMD_ESCALATE (or --escalate) configures a prefix such as sudo -n for privileged calls in the system scope; it is never applied to list or to any read-only query, and never when already running as root.
Added the link install method (LINK, SYSTEMD_INSTALL_METHOD, SYSTEMD_LINK_DIR): rendered units are kept in a directory the deploying user owns and systemctl link places the symlink, so only polkit authorization is needed, never file system privileges.
scope is now always in the template context, so one unit template can serve both scopes.
Every systemctl call now passes --no-ask-password so a missing authorization fails instead of prompting.

Initial Release.
Requires Python 3.11 or later and Django 5.2 or later.
Apps bundle systemd unit templates in a systemd/ directory. The set of templates matching SYSTEMD_TEMPLATES forms the project’s unit manifest (project_units()).
The systemd management command provides list, render, install, uninstall, restart and reload, all driven by the manifest so deployments never name units.
render --context and install --source support rendering at package time and installing the pre-rendered units on the host.
Units are managed in the user scope only, through systemctl --user. Nothing runs as root.
unit_installed is sent with unit and destination for each installed unit.
Unit files are rendered with autoescaping off, since they are not HTML.