| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
not sure how permanent this will be, but for now it allows me to do some
things that would otherwise be hard.
|
| |
|
|
|
| |
this updates mollysocket as well as its config. Unfortunately, it still
seems to work about as badly as before.
|
| | |
|
| |
|
|
|
|
| |
This reverts commit a86a04f9e26854ec967c46a6ad3f015364fb91a6. It has
since been merged into nixpkgs master, and i'm unsure if i will continue
using it.
|
| |
|
|
|
|
|
| |
not sure if this is a good idea or not, but i always liked how the
IRC #voc-wok channel of the c3voc works, and I don't run my own IRC (nor
do i want to have my monitoring on infra that is not my own), so I built
a similar thing with matrix.
|
| |
|
|
| |
https://github.com/NixOS/nixpkgs/pull/278981
|
| |
|
|
| |
with thanks to networkException, who wrote the initial nix package.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
so it turns out ntfy can run a little smtp server, which monit can send
its alerts to, resulting in a halfway okayish monitoring setup. It
doesn't even require mucking about with `sendmail'!
Downside: this is still monit.
Upside: from what I've heard, the other monitoring tools don't actually
seem to be all that much better?
Now I only have to come up with reasonable checks for the stuff I want
to actually keep an eye on …
|
|
|
not sure if i like this yet, but it seems worth trying it out.
|
