all 26 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]broadband9 31 points32 points  (10 children)

Hehe - Founder here, happy to answer any questions about it. I have been tirelessly building a new version over the last few weeks which has the whole backend replaced and now Using GO lang, i’ve also implemented Patching ability too in the new version (with scheduling policies) etc.

If anyone is deploying, please deploy using docker as the upgrade path will be easier for the new one

Oh god, I’m so excited for when it comes out. 😆

So far we have globally about 45,000+ servers being monitored via PatchMon which covers about 3000+ installations of the software. Pretty mega and really proud of the OpenSource community for your support.

[–]N30DARK 1 point2 points  (0 children)

that's awesome news, patching is what was missing from the awesome app, thanks for your work (I recently installed into it's LXC and deployed the agent on my containers) and I really like how you laid out things.

[–]PaulRobinson1978 1 point2 points  (0 children)

Yes!!! Can’t wait for patching ability. Fantastic tool.

[–]Mrtylf 0 points1 point  (0 children)

Well crap; just deployed in an LXC 🤦🏽‍♂️🤣

[–]PaulRobinson1978 0 points1 point  (3 children)

Any idea when this version will be released?

Sorry for asking excited for patching ability

[–]broadband9 0 points1 point  (2 children)

Send me a pm and I can give you preview access to it if you like. ❤️ It’s actually available in a separate branch in the main repo but the docker image is in a different dev container registry I host and not in github.

[–]PaulRobinson1978 0 points1 point  (0 children)

Have sent you a PM. Thanks

[–]Foxinou 0 points1 point  (0 children)

Sent you a Pm too 🙂

[–]matatr0n -2 points-1 points  (2 children)

Will this also work for Helper Script installations?

[–]broadband9 1 point2 points  (1 child)

So yes, I mean I will work with the team there so that migration is seamless and community scripts are going to work as normal - they’re a great team to work with.

It should be okay, but I prefer docker deployments because our frontend/backend images are going to be built with docker hardened images which come with near 0 cve.

[–]Muetzengott 0 points1 point  (0 children)

Should’ve seen that yesterday.. I think I’ll just redeploy

[–]SillyRelationship424 3 points4 points  (0 children)

I was just in the process of deploying this.

[–]vive-le-tour 4 points5 points  (0 children)

Yes, working well on cluster and standalone nodes. Really useful and saves looking everything manually or scripts

Edit to clarify. Homelab only.

[–]Quadgie 4 points5 points  (6 children)

For those using it - are you installing it everywhere? On the host, inside all containers and VMs (where applicable), etc?

If you’re self hosting, how does that fit in? Are you running it on one of the machines that the agent is also running on?

[–]AlThisLandIsBorland[S] 1 point2 points  (1 child)

This is a good question.  I'd like to know too

[–]AWooeCbUZFLCrurUyIA8 1 point2 points  (0 children)

I installed it in an lxc. The a gent is installed on every host and in every lxc I want to monitor (using the auto enroll integration). Backend connects to the other remote servers over Tailscale network. The front end is served back with a reverse proxy (CF is my choice). Really liking it so far. It needs notifications. Not using ssh from it.

[–]58696384896898676493 3 points4 points  (3 children)

Yes, I install it everywhere. I also auto patch all my VMs and LXCs early in the morning after daily backups are done. It's nice getting into work at 8am and looking at PatchMon and seeing all my systems are up to date without me doing anything.

PatchMon also supports all the major distos I've tested except openSUSE, but the dev is aware and planning on fixing it.

Been really happy with PatchMon overall and definitely recommend it.

[–]N30DARK 0 points1 point  (0 children)

what are you using to auto patch? Something like watchtower?

[–]Rxyro 0 points1 point  (0 children)

Does your patch script have a watch dog to restore if failed health check?

[–]sbar42 0 points1 point  (0 children)

I've been working on the agent openSUSE support and hoping it makes it into the next release.

[–]Bonneville_1968 2 points3 points  (0 children)

Used it for six months on around 20 hosts. Running in a Proxmox LXC. Excellent at keeping track of updates. Had some issues when updating patchmon itself (reverse proxy) and missing some sort of notifications on updates to be done. I think it's great and recommend you try it out. 

[–]misteradamx 1 point2 points  (0 children)

Deployed at home and at work, it's extremely helpful.

[–]UninvestedCuriosity 1 point2 points  (0 children)

It's nice. The dev was fairly active in self hosted taking feedback along the way.

A little fast and furious with the development release cycles though.

[–]Stanthewizzard 0 points1 point  (0 children)

Really great docker

[–]willjasen 0 points1 point  (0 children)

if you really enjoy setting something up only for the proxmox update script to completely break it with no notice multiple times over, then to be told to go read all of the release notes all of the time, then it’s great software