5 ms·
One Go binary, one YAML file, one SQLite database: I wrote my monitoring tool
- JensRantil 24d agoNice! But you made a mistake of using smallcaps-only on the repository. MacOSX file systems will complain and all sorts of weirdness can happen.
- aster0id 24d agoRecently I vibe coded a couple of scripts invoked by cron to do the same thing for a few services running on a single node for me. Works beautifully.
- nzoschke 24d agoSingle Go binary + SQLite database all the way. I've been doing this architecture on single tenant VMs for like 6+ years now and it has so many advantages for deployments, security and scaling. Pretty much every new tool and agent computer I set up uses this pattern. I've blogged about it and created a template repo. https://housecat.com/blog/the-hugs-stack-hypermedia-unix-go-sqlite https://housecat.com/blog/the-hugs-stack-hypermedia-unix-go-... https://github.com/housecat-inc/scratch https://github.com/housecat-inc/scratch
- fjcururuvy7 24d agoCan you share more about the single tenant vm setup?
- killingtime74 24d agoI like it but use Rust instead
- brvier 24d agoLoL
- anramon 24d agoWhere's the ai-written software and blog notice?
- brvier 24d agoIt's ai translated, English isn't my native language. And repo is ai documented. AI is everywhere, there is no reason to put notice on everythings. Move with your time. I don't put notice on everything that I build it on linux.
- applfanboysbgon 24d agoThere is a literal 0% chance this article was translated from human-written text in another language. Maybe you mean the article was AI-generated in your native language and then also translated by AI? That's quite a deceptive phrasing you used. > there is no reason to put notice on everythings. Move with your time. That is, in fact, the literal purpose to putting notice on everything. Put a notice so we know to move on with our time! If you can't be bothered to even write why your project is interesting, it's rather absurd to expect other people to spend time reading it.
- brvier 24d agoet pourtant ...
- 7bit 24d agoWho cares
- chews 24d agoIve used pocketbase (basically the same pattern with some nice dashboard magics) for soo many tasks like this it’s insane.
- brvier 23d agoI often use also pocketbase for small projects. It's a nice base (and nice project) when you need users management and a quick admin tool.
- boringstack 24d ago[dead]
- throw-the-towel 24d agoSimplicity rocks!
- wernerb 24d ago> The classic answer is a monitoring platform: ....... All great tools. But for a few dozen checks, I did not want to operate a second distributed system just to know whether the first one is up. There is advantage to keeping to "classic" tooling especially if you are not in an "I" context but in a "team" context. How large is the team that is going to use and maintain this custom tooling?
- brvier 23d agoIt s a tradeoff, here we have 20 products, 2 devs. There is less maintenance in such small tool, than in classic prometus/graphana/zabbix. This is exactly what I say, use "classic" tooling in a team. No need of a panzerfaust to kill a mosquito.