**#A quick edit to address something important and provide a disclaimer: **

Thank you all for your feedback! This project was “vibecoded” with Cloude AI and serves more as a “proof of concept” for what could be achieved with AI assistance. I’m just a tech enthusiast, and I’m excited to continue exploring new possibilities. I understand there’s a real concern about “AI Slop,” but that’s exactly why I’m sharing this project with you all so that experts who are interested in the idea can offer guidance or even help improve it.

I’ve noticed that many people with home labs prefer to update their applications manually instead of relying on other apps that automate the process. Often, they have to check each one individually. That’s where Vigil comes in. The primary function of Vigil is to centralize the information and give users clear visibility of which applications are outdated, their current version, and the newer version available from several sources. This way, you can decide what and when to update.

To be honest, I hope it ends up being useful to others as it is for me.

If you have a few minutes, I’d really appreciate you trying it out and leaving a review or suggestions on the repo or even here. I’d do my best to answer most of the comments.

REPO: https://github.com/kumucode/vigil.git

  • zorro@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    20 hours ago

    Cool project. Building something that exactly fits a problem you have is one of the most liberating parts of programming!

    I wouldn’t worry too much about the people mad about you using AI. It’s a powerful tool and I would be silly to not make use of it. I guarantee that a everyone using the internet today has had their packets flow through some piece of “vibe code”.

    One of my favorite features is having the AI tool explain back what every part of the code does. I helps you build understanding of both the code itself and is an excellent place to find bugs!

    Keep it up

    • 1step@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      20 hours ago

      That’s actually a good idea. I was thinking about getting the features “working” as intended. I’ll give it a try to the “explain back” method and see how it goes. Thanks

      • zorro@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        20 hours ago

        I would always recommend getting the bare minimum working great before adding extra features. If you get too far into features, making foundational changes get significantly harder.

        • 1step@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          18 hours ago

          Totally agree with that. I was trying to keep things as simple as possible, but there was always a new thing to try. I’m currently not implementing anything new, just focusing on enhancing what is already there.