9 comments

  • wernerb 1 hour 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?

  • nzoschke 9 hours ago
    Single 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-... https://github.com/housecat-inc/scratch

    • fjcururuvy7 7 hours ago
      Can you share more about the single tenant vm setup?
  • JensRantil 11 hours 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 10 hours ago
      That’s… strange. Could you give an example?
    • brvier 3 hours ago
      ? Can you explain ?
  • anramon 6 hours ago
    Where's the ai-written software and blog notice?
    • brvier 2 hours 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 hour 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 hour ago
          et pourtant ...
    • 7bit 1 hour ago
      Who cares
  • aster0id 11 hours 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 3 hours ago
    Simplicity rocks!
  • killingtime74 8 hours ago
    I like it but use Rust instead
  • chews 4 hours ago
    Ive used pocketbase (basically the same pattern with some nice dashboard magics) for soo many tasks like this it’s insane.
  • boringstack 4 hours ago
    [dead]