Hypridle can now be started and managed using systemd with
systemctl --user enable --now hypridle.service
This is useful as it allows an easier way to manage services that, like this, always run in the background. This way systemctl start/stop/restart commands can be used instead of killall hypridle / nohup hypridle or similar. I slightly updated the README to mention this different usage possibility.
Before this is ready to be merged, though, I'd need some feedback on the way I am currently configuring and installing the service file (see CMakeLists.txt and systemd/hypridle.service.in). The configuration part is not currently working though, I'm not really sure what I should be using to point at the directory the hypridle executable can be found in (usually /usr/local/bin if no extra cmdline args are given to smake).
Also, LMK if anything else should be changed, of course.
Hypridle can now be started and managed using systemd with
This is useful as it allows an easier way to manage services that, like this, always run in the background. This way
systemctl start/stop/restart
commands can be used instead ofkillall hypridle / nohup hypridle
or similar. I slightly updated the README to mention this different usage possibility.Before this is ready to be merged, though, I'd need some feedback on the way I am currently configuring and installing the service file (see
CMakeLists.txt
andsystemd/hypridle.service.in
). The configuration part is not currently working though, I'm not really sure what I should be using to point at the directory the hypridle executable can be found in (usually/usr/local/bin
if no extra cmdline args are given to smake).Also, LMK if anything else should be changed, of course.