nixfiles - my nixfiles

	Commit message (Collapse)	Author	Files	Lines
2024-12-06	flora: replace mailserver with ntfy.sh	stuebinm	1	-4/+4
	not sure how permanent this will be, but for now it allows me to do some things that would otherwise be hard.
2024-12-05	mollysocket: update	stuebinm	1	-3/+3
	this updates mollysocket as well as its config. Unfortunately, it still seems to work about as badly as before.
2024-04-07	common/headless: basic monitoring on by default	stuebinm	2	-4/+42

2024-04-03	Revert "flora: test-deploy the mollysocket nixpkgs PR"	stuebinm	1	-3/+3
	This reverts commit a86a04f9e26854ec967c46a6ad3f015364fb91a6. It has since been merged into nixpkgs master, and i'm unsure if i will continue using it.
2024-03-27	help i wrote a matrix bot	stuebinm	1	-0/+31
	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.
2024-03-10	flora: test-deploy the mollysocket nixpkgs PR	stuebinm	1	-3/+3
	https://github.com/NixOS/nixpkgs/pull/278981
2024-03-04	init mollysocket package, module, and deploy it on flora	stuebinm	1	-2/+4
	with thanks to networkException, who wrote the initial nix package.
2024-02-29	flora: monit via ntfy sh	stuebinm	1	-3/+5
	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 …
2023-04-11	manage secrets with sops	stuebinm	1	-0/+35
	not sure if i like this yet, but it seems worth trying it out.