-6
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Aug 2026
-6 points (45.0% liked)
Selfhosted
61808 readers
338 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
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.
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. if you have to make multiple pairs, or update something in them, it gets old fast.
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.thank you. this creates it, but is there a way to view or edit its current configuration in a similar format? and this is not persisted, is it?
If you inspect the generated timer you see the same format in the OnCalendar line.
What do you mean by persisted? The service and timer will both be there as long as the timer doesn't end. Which it won't in my example.
If you want to copy it for later reference, you can simply copy the files.
but without the command
I mean saved to a file so that it will still be there after reboot
Yeah, but that's an easy one to parse, if you really need it.
I'm pretty sure if you use OnCalendar it will still be there after a reboot. Let me check.
EDIT: oh damn!! It doesn't persist on reboots. Sorry for this oversight.
Or just cron that calls a logger works well enough
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.
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.
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.
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.
But why does it need a cross platform package when systemd is available everywhere? What UX is better than the already existing cockpit?
is systemd available for windows and mac?
windows, yes: https://learn.microsoft.com/windows/wsl/systemd
for Mac you should probably use macOS's launchd services: https://www.launchd.info/
@WhyJiffie @selfhosted @helix
Just what those systems need to blow themselves away!!!!
Potty please!!