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
  • [object Object]@lemmy.caEnglish
    0·
    7 days ago

    I hope this doesn’t come off as too harsh, but the text reads as very AI generated, and I think if you rewrote the main text you could do a much better job.

    It’s not clear to me why to use it, the pitch today is that it makes failures loud, which is nice, but very poorly described.

    The tool itself looks good, but the website looks very “Claude”, especially the text at the top saying “ONE BINARY · LINUX · MACOS · WSL · 25 MB RAM IDLE”

    Those are great pros, but are they the guest thing the user should see?

    Honestly the first paragraph of the quick start is a much better pitch:

    RunWisp is one small Go binary. You list the shell commands you want to run in a runwisp.toml, and RunWisp takes care of the rest — firing jobs on cron, restarting services when they crash, and capturing every line of stdout and stderr so you can go back and look at what happened. There’s a TUI in your terminal and a Web UI in your browser for poking around. No external database, no agent, no sidecar

    This tool looks decent, but for me I find nix helps manage the complexity of systemd well

    • runwisp_com@lemmy.worldOPEnglish
      0·
      6 days ago

      actually not harsh

      this is exactly the kind of concrete feedback I was hoping for. You’re right that the quick-start paragraph explains the actual value better than the current pitch… Thank you for taking the time to look at this.

  • Helix 🧬@feddit.orgEnglish
    0·
    7 days 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.

    • WhyJiffie@sh.itjust.worksEnglish
      0·
      7 days 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. if you have to make multiple pairs, or update something in them, it gets old fast.

    • runwisp_com@lemmy.worldOPEnglish
      0·
      7 days ago

      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.orgEnglish
        0·
        7 days 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.worldOPEnglish
          0·
          7 days 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.