**#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.
Great idea. Automatic updates (e.g. Watchtower) make me a little nervous.
For me, it’s all about finding the right balance. I don’t want to have to manually update for every little bug fix version bump. Most software I find that major.minor version tags, if they exist, are a good compromise with daily auto updates unless it’s a really fast releasing software where just a major version makes sense. I usually just track releases on GitHub or wherever the source is hosted and bump as I need. That takes care of probably 90-95% of the containers I run.
Automatic updates for bug fixes (e.g. 1.0.0 to 1.0.1) are usually fine - it's major and minor updates that are scarier. I've never used Watchtower so I'm not sure if it has an option to only allow bugfixes.
That would depend on each project properly using semver, which is unlikely.
Personally, I just risk all the updates. It's not a huge deal to recover.
Yeah, I'm a developer and my teammates don't always follow semver standards. I try to but every now and then it's really hard to know which is the right move. I've also had breaks because of minor increments and the author refused to roll back the change because the new behavior was consistent with the spec [that didn't change].
Yeah that's exactly what I was thinking about when I started this project. I've noticed that many home labers are a bit skeptical with automatic updates. I'm glad you liked the idea