RunWisp · Schedule, supervise, observe. One binary.
runwisp.com
The open-source cron replacement and process supervisor with a built-in web dashboard. One binary, one TOML file, zero runtime dependencies.

I created a tool that’s easy to set up and gives you fast and beautiful web UI and TUI from a single Go binary.

It can serve both as a cron replacement, or just as a cron supplement - let’s say, to version control your cron tasks in a small team. It also has an alert system that allows you to send slack/discord/telegram/email when something bad happens.

I want your feedback. You can help me shape this product into something people will find pleasant to use.

This daemon is copyleft GPL-3.0-or-later - completely free to use.

RunWisp is currently in pre-release phase but is slowly approaching its v1.0 stable release.

Website: https://runwisp.com/

GitHub repo: https://github.com/runwisp/runwisp - feel free to open an issue!

Quick start: https://docs.runwisp.com/getting-started/quick-start/

AI Disclosure

  • Design - Hint
  • Implementation - Pair
  • Testing - Assisted
  • Documentation - Pair
  • Review - Hint
  • WhyJiffie@sh.itjust.worksEnglish
    1·
    5 hours ago

    If you inspect the generated timer you see the same format in the OnCalendar line.

    but without the command

    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.

    I mean saved to a file so that it will still be there after reboot

    • Helix 🧬@feddit.orgEnglish
      1·
      2 hours ago

      but without the command

      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.