Can you share more about the single tenant vm setup?
wernerb 1 days 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 16 hours ago [-]
It 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.
JensRantil 1 days ago [-]
Nice! But you made a mistake of using smallcaps-only on the repository. MacOSX file systems will complain and all sorts of weirdness can happen.
WalterGR 1 days ago [-]
That’s… strange. Could you give an example?
brvier 1 days ago [-]
? Can you explain ?
anramon 1 days ago [-]
Where's the ai-written software and blog notice?
brvier 1 days ago [-]
It'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 1 days ago [-]
There 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 1 days ago [-]
et pourtant ...
7bit 1 days ago [-]
Who cares
aster0id 1 days ago [-]
Recently 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.
throw-the-towel 1 days ago [-]
Simplicity rocks!
chews 1 days ago [-]
Ive used pocketbase (basically the same pattern with some nice dashboard magics) for soo many tasks like this it’s insane.
brvier 22 hours ago [-]
I 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.
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-... https://github.com/housecat-inc/scratch
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?
This is exactly what I say, use "classic" tooling in a team. No need of a panzerfaust to kill a mosquito.
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.
> 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.