c6ebcfe66e
servo: port legacy /var/lib users over to "method = bind" persistence
...
i may wittle these down in the future
2024-02-23 15:49:54 +00:00
28d4a4b065
persistence: move stores behind a byStore attr to support disabling persistence altogether (for e.g. rescue image)
2023-11-08 15:33:15 +00:00
ec4b974f3d
matrix-synapse: auto-register the ntfy-sh push gateway at launch
2023-10-24 14:47:59 +00:00
c59e9b09fc
matrix: document push notification configuration
2023-10-22 14:47:52 +00:00
865777b7ba
enable ntfy (and manually integrate with matrix)
2023-09-23 21:09:04 +00:00
0a519eddb4
persist: allow persisting of individual files, not just directories
...
i actually do already, with ~/.ssh/id_ed25519 -- it works only as a fluke
2023-07-08 01:31:14 +00:00
4fd4efa22f
DNS: split the zone generation out of trust-dns
...
this is in preparation for upstreaming parts of this into nixpkgs
2023-06-08 00:32:28 +00:00
fb427e55e8
secrets: define these by crawling the repo to decrease duplication
2023-05-14 09:50:01 +00:00
96eb427ea7
matrix: support larger uploads (100M)
2023-05-03 22:22:09 +00:00
6af0d54e7b
matrix: re-enable signal bridge
2023-04-18 06:10:17 +00:00
781a149542
matrix: re-enable IRC bridge
2023-04-16 00:32:04 +00:00
403b177a80
matrix: disable mautrix-signal (temporarily)
2023-03-11 00:02:30 +00:00
f3568462c2
fix matrix-synapse after nixpkgs update
2023-01-25 03:46:05 +00:00
d13bcc49ab
refactor hosts directory, and move ssh keys out of modules/data
...
longer-term, i want hosts/by-name to define host-specific data
that's accessible via the other hosts (things like pubkeys).
also the secrets management needs some rethinking. there's really not
much point in me specifiying where *exactly* a secret comes from at its
use site. i should really be specifying secret store manifests; i.e.
"servo.yaml contains secrets X Y and Z", and leaving the rest up to
auto-computing.
2023-01-19 23:23:43 +00:00
