[–] [S] -3 points 3 days ago* (last edited 2 days ago) (3 children)

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.

  • source
  • parent
  • context
  • [–] [S] 2 points 3 days ago (4 children)

    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.

  • source
  • parent
  • context
  • [–] [S] -1 points 4 days 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.

  • source
  • parent
  • context
  • [–] [S] 1 point 4 days ago (6 children)

    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.

  • source
  • parent
  • context
  • [–] [S] 1 point 4 days ago* (last edited 4 days ago) (1 child)

    Copilot was listed as a contributor on an early commit because I used it to help draft that commit. that attribution overstates its role in the overall project. The disclosure in the post is the more accurate summary of how AI was used.

  • source
  • parent
  • context
  •  

    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
    [–] 7 points 4 weeks ago

    cron isn't using your login shell. that's the trap.

    but put PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin at the top of the crontab, then test the exact command once with env -i HOME="$HOME" PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /bin/sh -c '...', and you catch most of the "worked in my terminal" stuff before it turns into tomorrow's missing backup. MAILTO or a heartbeat catches the next failure.

  • source