summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
|
* home: add twelfstuebinm2024-02-111-0/+8
| | | | | | for Chris Marten's logic course. Uses an unofficial version from github since the actually released version is so old that the elisp code for the emacs mode doesn't work with an up-to-date emacs anymore.
* headless: don't do documentationstuebinm2024-02-112-1/+11
| | | | (except for man pages — without these, somehow deploy-rs breaks)
* update inputsstuebinm2024-02-111-18/+18
|
* pkgs: init bookwyrmstuebinm2024-02-117-3/+196
| | | | | | | this is still missing: - a nice way to do settings - lots of testing (run the manage.py test script in a nixos test?) - an actual way to deploy this in a halfway reasonable way
* update inputsstuebinm2024-02-111-31/+15
|
* guixify surltesh-echerstuebinm2024-02-116-64/+224
| | | | | | | | initial config, the system is now a mess with lots of old nix stuff still hanging out on the disk. Tbh not sure if I'll do much with this, but wanted to play around a little with this again.
* home/ssh: add amatl configstuebinm2024-01-291-0/+5
|
* home: new newsfeedsstuebinm2024-01-291-0/+2
|
* blog: css rewritestuebinm2024-01-291-4/+4
|
* new webring entriesstuebinm2024-01-292-0/+41
|
* git.infra4future.de can't do ipv6stuebinm2024-01-231-0/+6
| | | | something something nftables module obscurity
* update inputsstuebinm2024-01-222-16/+16
|
* home: fix $MANPAGER with batstuebinm2024-01-211-0/+1
| | | | | | turns out there's an issue for that: https://github.com/sharkdp/bat/issues/2563 and even a hint in bat's README.md
* update inputsstuebinm2024-01-182-20/+20
|
* akkoma: disable link previewsstuebinm2024-01-151-4/+1
| | | | they sometimes hang until akkoma gets reaped by the oom killer
* home: shell function to add emojis to akkomastuebinm2024-01-131-0/+16
|
* nomsable webringstuebinm2024-01-138-2/+90
| | | | (just messing around for now)
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 05:46:14 +0000