355c91e194
nix/os/devices/sj-srv1: bump versions
2025-03-29 14:22:57 +01:00
ec51fe9501
nix/os/devices/sj-srv1: bump versions
2025-03-29 14:17:53 +01:00
1429fd02a4
nix/os/devices/sj-srv1: bump versions
2025-02-11 10:10:00 +01:00
c06d2e19bf
nix/os/devices/sj-srv1: bump versions
2025-01-23 10:01:23 +01:00
50804cb67e
nix/os/devices/sj-srv1: bump versions
2024-12-23 22:17:58 +01:00
5cb20fcb5d
nix/os/devices/sj-srv1: bump versions
2024-12-06 09:34:12 +01:00
63907b1b17
nix/os/devices/sj-srv1: bump versions
2024-12-05 22:11:05 +01:00
56955abbe8
nix/os/devices/sj-srv1: bump versions
2024-10-22 17:07:45 +02:00
4c71887ea6
feat(router0-dmz0, sj-srv1/containers/webserver): set up kanidm
2024-10-16 23:03:38 +02:00
32c17a671f
nix/os/devices/sj-srv1: bump versions
2024-10-10 09:05:01 +02:00
79da6a79cc
nix/os/devices/sj-srv1: bump versions
2024-10-10 09:02:21 +02:00
547e0f6305
nix/os/devices/sj-srv1: bump versions
2024-08-16 16:29:52 +02:00
34417fb7bc
nix/os/devices/sj-srv1: bump versions
2024-08-16 15:52:33 +02:00
1533077234
sj-srv1,containers: debug and streamline networking config; update and track forgejo here
...
after an update to nixpkgs on sj-srv1 the networking for the `webserver`
container wasn't working. this caused me to debug the situation and
changing lots of things around. the culprit was most likely some impure
state file on the server that caused the `ve-webserver` interface not to
persist its IP. after renaming the webserver container the problem went
away.
i reverted all the IP changes and am keeping the other changes as opporunistic
improvements
2024-07-26 18:02:52 +02:00
122d4072bb
sj-srv1: nix flake update
2024-07-26 14:39:24 +02:00
92be66cbb5
nix/os/devices/sj-srv1: bump versions
2024-07-26 14:38:46 +02:00
fce6072032
nix/os/devices/sj-srv1: bump versions
2024-07-26 14:38:46 +02:00
7d113c3257
nix/os/devices/sj-srv1: bump versions
2024-06-01 14:07:47 +02:00
2c84e79f4a
sj-srv1: init with restic backup
2024-02-08 21:02:59 +01:00
