summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* surltesh-echer: update guix, fix guix channel in home configstuebinm2024-04-102-23/+16
| | | | | | thanks to change Id90e1e1ff399afe54fff68167f497f0484d2c218 being merged into guix (d082573db1b86d922965dc746627bf0f0cc18af4), the hikari package from upstream is no longer broken.
* update inputsstuebinm2024-04-091-15/+15
|
* meta: extra module docs in `man configuration.nix`stuebinm2024-04-081-2/+3
| | | | | | all non-nixos modules I use should have their documentation merged into the configuration.nix man page I have available on ilex / abbenay, even for modules not used there.
* home: add ijqstuebinm2024-04-071-1/+1
| | | | because for some reason it's not there already
* home: funny jq for geojson → gtfs shapes.txt conversionstuebinm2024-04-071-0/+1
|
* home: glow → lowdown for markdown viewingstuebinm2024-04-072-2/+5
| | | | | lowdown isn't very good, but at least it doesn't have any weird cloud features (why is this the standard for things that show text??)
* common/headless: basic monitoring on by defaultstuebinm2024-04-077-37/+91
|
* chaski: restart the ntfy bot if failedstuebinm2024-04-031-0/+1
|
* update inputsstuebinm2024-04-031-12/+12
|
* Revert "flora: test-deploy the mollysocket nixpkgs PR"stuebinm2024-04-035-26/+6
| | | | | | This reverts commit a86a04f9e26854ec967c46a6ad3f015364fb91a6. It has since been merged into nixpkgs master, and i'm unsure if i will continue using it.
* home: more news feedsstuebinm2024-04-021-1/+3
|
* element-web: nicer coloursstuebinm2024-04-022-4/+5
|
* flora/element-web: correct patch for left side barstuebinm2024-03-291-7/+5
| | | | | | | without this, there's lots of extra space since the in-javascript layout script thinks boxes take up more space than they actually do (i think there was this nice idea, once, about separating the UI from the rest of the application? ah well)
* flora: schildichat-web → element-webstuebinm2024-03-283-1/+165
| | | | | | | | | | | | | 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 …
* help i wrote a matrix botstuebinm2024-03-277-5/+98
| | | | | | | 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.
* update inputsstuebinm2024-03-262-18/+16
| | | | also remove v4l2loopback on ilex
* update inputsstuebinm2024-03-163-14/+14
| | | | let's see if this hydra of mine is of any use :)
* home: two new feedsstuebinm2024-03-161-0/+2
|
* home: minor tweaksstuebinm2024-03-163-2/+11
|
* home: i have officially lost control of all the git reposstuebinm2024-03-151-0/+10
| | | | | | | | | | | | | | | so I added a command to search though them :) Should help whenever I'm not sure if I have cloned something already. Intended usage is something like `cd (git where)`. It might be useful to extend this so it doesn't assume everything has a remote called `origin', but looks like my only three git repos which don't have one (and which are not my own) where cloned via heartwood/radicle, and I'm unlikely to need those again tbh. … tbh, it might also be worth it to add a mass-fetch command? So much of what I've cloned is just old stuff lying around …
* pkgs/scripts: monit->prometheus converterstuebinm2024-03-112-0/+149
| | | | | | | | | 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).
* update deploy-rsstuebinm2024-03-102-11/+39
| | | | | | new feature which made this relevant is use of interactive sudo (since abbenay still has interactive sudo from the days when it was a desktop machine)
* flora: test-deploy the mollysocket nixpkgs PRstuebinm2024-03-105-6/+26
| | | | https://github.com/NixOS/nixpkgs/pull/278981
* abbenay: run a hydra instance for funstuebinm2024-03-103-3/+32
|
* add hydraJobs outputstuebinm2024-03-101-0/+4
|
* home: useful nix toolsstuebinm2024-03-081-0/+2
|
* home-minimal: useful git branch sorting defaultstuebinm2024-03-071-0/+1
|
* home: add git annex remote for amatlstuebinm2024-03-073-3/+16
| | | | | the tool is still a bit rough, but it should work well enough for actual use (even if i have to restart xochitl afterwards)
* home-minimal: dogdns → doggo, punycode via libidnstuebinm2024-03-072-2/+4
| | | | | | | doggo is more maintained, can use IPv6, queries all nameservers at once by default, and generally feels comfier. (now if only it had a man page ..)
* monit: add stuff for infra4future.destuebinm2024-03-071-1/+13
|
* restructure & general cleanupstuebinm2024-03-0519-167/+36
| | | | | | | | - 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-042-3/+2
| | | | | | 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-047-3/+152
| | | | with thanks to networkException, who wrote the initial nix package.
* monit: extra catch-all check via systemctl is-system-runningstuebinm2024-03-041-0/+3
|
* home: small stuffstuebinm2024-03-043-1/+5
|
* monit: some kinda reasonable checksstuebinm2024-03-042-5/+36
|
* noms.ing: redirect webring.noms.ing → noms.ingstuebinm2024-02-291-1/+1
| | | | | since that website doesn't contain anything anyways, but people started linking to it.
* flora: monit via ntfy shstuebinm2024-02-294-3/+45
| | | | | | | | | | | | | | 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 …
* desktop: add noto cjk fontsstuebinm2024-02-221-1/+8
| | | | | though it seems a little blurry at low resolutions. might have to tweak stuff / see if i can find a better font.
* home: new feedsstuebinm2024-02-211-0/+3
|
* update inputsstuebinm2024-02-213-60/+14
|
* modules/bookwyrm: expose in flake.nixstuebinm2024-02-151-1/+4
|
* modules/bookwyrm: add a nixos teststuebinm2024-02-152-0/+68
| | | | because like, why not learn how to use these out-of-tree?
* modules/bookwyrm: manage.py wrapper needs env filestuebinm2024-02-152-4/+9
| | | | otherwise it just fails to start with an error
* modules/bookwyrm: use environmentFile for secretsstuebinm2024-02-152-10/+51
| | | | | | | | | | this allows setting options via an environment file that is passed to the systemd units, in addition to the ones set during build time of the package. For now this is tailored to SECRET_KEY, but it may be useful for other settings as well (e.g. EMAIL_HOST_PASSWORD), and I'm not sure if it takes priority over the build-time settings ...
* modules/bookwyrm: whoops, that's not how the module system worksstuebinm2024-02-141-14/+25
|
* modules/bookwyrm: initstuebinm2024-02-142-4/+186
| | | | | | | | this should be mostly usable for actual deployments. Only thing that's really still annoying is having to set the SECRET_KEY via Nix, since not having set it makes the package fail to build. But it doesn't actually end up in the derivation, so changing it afterwards should be fine; I've just not tested that yet.
* pkgs/bookwyrm: allow setting .env settingsstuebinm2024-02-131-76/+80
|
* home: tweak git configstuebinm2024-02-111-0/+3
|
* home: tweak newsboat configstuebinm2024-02-112-3/+11
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-23 05:08:07 +0000