If systemd timers, journald and cockpit already cover your needs, RunWisp probably isnt for you. RunWisp is aimed at people who want portable TOML-defined tasks and services with unified history, logs and alerts. you’re right that ACLs are currently missing, but access is protected by password authentication and the UI can only trigger commands already defined on the host.
helix@feddit.org 21 hours ago
Looks good, but kind of superfluous if you just use systemd timers, lol
Systemd timers are the modern way of doing it which gives you everything you coded this tool for, logs and whatnot, in the journal.
And you can run them in a web UI like cockpit aswell.
This might be interesting in a business setting but lacks ACLs and user management in general.
It’s probably also quite easy to hack the system with it if you can inject some malicious scripts.
runwisp_com@lemmy.world 20 hours ago
helix@feddit.org 19 hours ago
Yes but… Systemd timers are INI-defined tasks and services with unified history and logs, the alerts can be easily added with any alerting system.
runwisp_com@lemmy.world 17 hours ago
yeah, thats fair, systemd + cockpit with alerts can cover pretty much the same ground. What RunWisp brings is the integrated cross-platform package and UX. Nobody is claiming that those underlying capabilities are impossible to assemble elsewhere.
helix@feddit.org 15 hours ago
But why does it need a cross platform package when systemd is available everywhere? What UX is better than the already existing cockpit?
kittenz@lemmy.blahaj.zone 20 hours ago
Or just cron that calls a logger works well enough
runwisp_com@lemmy.world 19 hours ago
if cron + logger covers your needs, you should keep that going. RunWisp is for cases where you also want searchable run history with retention and rotation, failure alerts, manual triggering and service supervision, all in one place without assembling those pieces yourself.
WhyJiffie@sh.itjust.works 14 hours ago
I generally like some things that syatemd gives, but is there an easier way to create timed automations with systemd timers?
with cron, its just a single line with the recurrence pattern and the command. with systemd, you have to create a timer unit file with several lines, a service unit file with several lines, put them in the right directory, reload systemd, enable the timer. timers are not difficult, but much more convoluted than the crontab.
helix@feddit.org 8 hours ago
here’s a single line for you which creates a one-shot service+timer in one go, suspending the system in 4 hours:
If you want it to run repeatedly, simply replace
–on-activewith–on-calendar=“*-*-* 04:00:00”for example.