summaryrefslogtreecommitdiff
path: root/flora (follow)
Commit message (Collapse)AuthorAgeFilesLines
* monitoring: add cloud.infra4future.de via httpsstuebinm2024-07-041-0/+4
|
* monitoring: check nobelium via httpsstuebinm2024-07-011-2/+2
| | | | | | openssh starts to deny recurring connections that don't try to authenticate after a while, which seems to be what monit is doing for the ssh check.
* monitoring: check that nobelium is runningstuebinm2024-06-271-0/+4
| | | | | … might be good to also add a monit on nobelium itself, but in any case this isn't wrong either.
* yeet the nix flakesstuebinm2024-04-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | this is, in the widest possible sense, a revert of e88fed18f499a3e8ac98c772bbb62f00d1f8d1d7, which was now a little over two years ago. Of course, lots of things have changed since then: - this uses npins instead of niv, which is both simpler and still maintained - i haven't brought back the old deploy lib; I still use deploy-rs (with some modifications) to deploy things - if you actually use my stuff downstream, you can now use packages/ & tests/ & modules/ as entry points directly, while still having some control over inputs - (since i also don't believe any downstream users actually exist, i've not bothered to have a shim flake.nix so your stuff probably just broke. well, it was an experimental feature, anyways) - in general there's a lot more of the old-fashioned structure back again, with default.nix files in subdirectories that form a structure, not like how almost everything was just imported in the one big flake.nix file For people who are interested in also having a non-flake config similar to this one, it's probably best to take a look at inputs.nix (and also at npins, of course)
* common/headless: basic monitoring on by defaultstuebinm2024-04-072-32/+2
|
* Revert "flora: test-deploy the mollysocket nixpkgs PR"stuebinm2024-04-031-1/+1
| | | | | | This reverts commit a86a04f9e26854ec967c46a6ad3f015364fb91a6. It has since been merged into nixpkgs master, and i'm unsure if i will continue using it.
* flora: schildichat-web → element-webstuebinm2024-03-281-1/+1
| | | | | | | | | | | | | since schildichat-web has essentially been unmaintained for a while now, i guess i don't really have any choice here. I've tried to at least hack a little css into my element so it won't bother me too much (mostly making UI elements smaller & changing some colours). However, it turns out they do UI calculations in javascript which just make hard assumptions over values set in the css, and so far I've not succeeded in fixing these. Das ist doch wirklich alles Unsinn in diesem Ökosystem …
* pkgs/scripts: monit->prometheus converterstuebinm2024-03-111-0/+9
| | | | | | | | | Not sure yet how much (if anything) I'll actually do with this, but it seemed like a fun idea to try and it's been way to long since I wrote anything in scheme. Entirely untested, as I don't actually have a prometheus running atm (apart from the one specifically for tracktrain on chaski).
* flora: test-deploy the mollysocket nixpkgs PRstuebinm2024-03-101-1/+1
| | | | https://github.com/NixOS/nixpkgs/pull/278981
* monit: add stuff for infra4future.destuebinm2024-03-071-1/+13
|
* restructure & general cleanupstuebinm2024-03-056-180/+7
| | | | | | | | - pkgs/ should now also contain all package overrides - pkgs/patches/ now contains all patches - nix flake info succeeds again - still not sure what to do about scripts - services which are not used should not be kept around this long
* import custom modules by defaultstuebinm2024-03-041-2/+0
| | | | | | which has the nice side-effect that they now show up on my `man configuration.nix'. (also I don't have to manually import things anymore)
* init mollysocket package, module, and deploy it on florastuebinm2024-03-042-0/+14
| | | | with thanks to networkException, who wrote the initial nix package.
* monit: extra catch-all check via systemctl is-system-runningstuebinm2024-03-041-0/+3
|
* monit: some kinda reasonable checksstuebinm2024-03-041-4/+35
|
* flora: monit via ntfy shstuebinm2024-02-293-0/+40
| | | | | | | | | | | | | | 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 …
* akkoma: disable link previewsstuebinm2024-01-151-4/+1
| | | | they sometimes hang until akkoma gets reaped by the oom killer
* nomsable webringstuebinm2024-01-131-0/+11
| | | | (just messing around for now)
* apparently i run a mumble nowstuebinm2023-12-293-0/+30
|
* huh, looks like i bought another domainstuebinm2023-12-091-0/+6
|
* jump to nixos 23.11stuebinm2023-11-301-1/+1
|
* update inputsstuebinm2023-08-041-3/+0
|
* assorted nice-ish thingsstuebinm2023-08-032-23/+1
|
* element → schildiChatstuebinm2023-08-011-1/+1
|
* try out a ntfy on florastuebinm2023-08-012-0/+36
| | | | (with thanks to emilyy's nix config; let's see if this makes sense for me)
* update inputsstuebinm2023-06-301-1/+1
|
* akkoma: workaround for a certain linkstuebinm2023-06-291-0/+4
| | | | | this crashes the rich media link preview thingie. Maybe I will have motivation to look into why …
* tenpo ni la, akkoma sona e ni: toki pona li toki.stuebinm2023-06-233-1/+85
|
* host my own element, for $reasonsstuebinm2023-06-232-0/+31
|
* akkoma: reject list go nomsstuebinm2023-06-171-0/+1
|
* initial jump to nixos 23.05stuebinm2023-05-292-23/+2
|
* akkoma: reject mstdn.socialstuebinm2023-05-281-0/+1
|
* akkoma: reject another instancestuebinm2023-05-211-1/+4
| | | | no idea who this is, they just plopped up suddenly
* akkoma: add TOSstuebinm2023-05-041-0/+5
|
* akkoma: reject mastodon.socialstuebinm2023-05-041-1/+8
|
* manage secrets with sopsstuebinm2023-04-113-5/+19
| | | | not sure if i like this yet, but it seems worth trying it out.
* flora: use gitMinimal everywherestuebinm2023-03-241-3/+3
| | | | | this is probably not strictly necessary (git & gitMinimal should deduplicate nicely), it's just weird to have two of them.
* update inputsstuebinm2023-03-243-2/+11
| | | | | | | | | also remove some old stuff. also deduplicate the erlangs on my akkoma. also remove chromium, since for some reason hydra hasn't built it yet and I'm not fancying compiling it myself. also remove the whole sshd mosh stuff for the chat, since that broke tmux-on-login.
* fix things & make some others simpler, also ipv6 🎉stuebinm2023-03-052-24/+1
|
* flora: don't have an akkoma that depends on X / GTK+stuebinm2023-02-201-1/+6
|
* update inputsstuebinm2023-02-201-1/+1
|
* further akkoma stuff because templating elixir hardstuebinm2023-02-161-2/+2
| | | | | … why do we do that, again? But this module has no escape hatch, so I guess I just spend ~twenty minutes on "how do i make an atom"
* more akkoma stuffstuebinm2023-02-162-32/+40
|
* flora: jump to akkoma @ nixpkgs-unstablestuebinm2023-02-161-83/+88
|
* flora/cgit: unbreak smart http gitstuebinm2023-02-131-0/+2
|
* blog: add lux bookstuebinm2023-02-131-0/+18
|
* update to nixos22.11stuebinm2022-12-053-38/+1
|
* update inputsstuebinm2022-11-121-5/+1
|
* remove some old stuffstuebinm2022-10-043-101/+1
|
* cgit hopefully change default branchstuebinm2022-09-142-1/+31
| | | | | | | kinda annoying that i don't get idle-indicators for repos that don't have a master-branch. not sure if this'll fix it though, cgit is weird.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 21:25:13 +0000