**#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

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

    I think documenting everything is key so people can clearly see the progress. I didn’t know that you could merge the changes to the main branch and that it is a core skill as you mentioned. I kind of noticed exactly what you said “it may change other parts of that file that you didn’t ask for” while doing some tweaks. This AI topic has too many branches and it’s a fascinating topic for debates. Thanks for taking the time to give this advice.