2
[AIP] I've been working on the perfect UI for cron and supervisor for several months now. Tell me what you think. (runwisp.com)
submitted 5 hours ago* (last edited 3 hours ago) by to c/selfhosted@lemmy.world
15 comments fedilink hide all child comments
 

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
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 4 hours ago (2 children)

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.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 2 points 3 hours ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 hours ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 41 minutes 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 3 hours ago (1 child)

    Or just cron that calls a logger works well enough

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 3 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.

  • permalink
  • fedilink
  • source
  • parent