cd5cfe2bb2
[overwatch] init
2025-01-21 23:11:31 +01:00
6112a59af7
[microvms] rm nameserver option
2025-01-21 23:10:44 +01:00
4e684de843
[nextcloud] proxyforward from htznr
2025-01-21 22:50:40 +01:00
1e73794b18
[fanny] set nix tarball-ttl 0
...
otherwise microvm-update uses cached flake instead upstream
2025-01-21 22:44:43 +01:00
e2b3f4a754
[sops] add nextcloud hostkey
2025-01-21 22:04:40 +01:00
2fc4da9244
[nginx] proxy forward host
2025-01-21 21:25:42 +01:00
0ed00541ff
Revert "[modules] move microvm module import from makeMicroVM to baseModules"
...
This reverts commit 3861daaf76
2025-01-21 21:02:03 +01:00
eafe7a6b95
[vpn] update dummy secrets
2025-01-19 23:48:02 +01:00
fe9ff06aae
[lucia] init dummy secrets
2025-01-19 23:47:50 +01:00
ba6e219d64
[fanny] init dummy secrets
2025-01-19 23:47:41 +01:00
7431209bc2
[durruti] rm secrets.yaml - currently empty
2025-01-19 23:44:51 +01:00
5f780e17eb
[nextcloud] add dummy secrets
2025-01-19 23:39:51 +01:00
fda348f5da
[sops] add a dummy key to allow secret usage within test vms
2025-01-19 22:55:54 +01:00
68b3da7df8
[fanny] proxypass cloud.malobeo.org
2025-01-19 14:53:39 +01:00
affcc71eb1
[fanny] deploy nextcloud
2025-01-19 14:52:33 +01:00
4462856fa0
[nextcloud] rm obsolete nameserver
2025-01-19 14:52:20 +01:00
ahtlon
fabf48a5c0
[nextcloud] nextcloud works now
2025-01-19 14:22:08 +01:00
ahtlon
9b4cd02e53
[nextcloud] enable postgress, redis, change domain
2025-01-19 14:22:08 +01:00
ahtlon
fab1b18263
[nextcloud] rm discourse
2025-01-19 14:22:08 +01:00
cbd041f563
[nextcloud] fix hostname
2025-01-19 14:22:08 +01:00
ahtlon
ef25c686b4
add nextcloud collectives
2025-01-19 14:22:08 +01:00
ahtlon
66392ca2c2
login geht
2025-01-19 14:22:08 +01:00
ahtlon
9afa8987e7
nextcloud minimal
2025-01-19 14:22:08 +01:00
ahtlon
0239733e62
sops....
2025-01-19 14:22:08 +01:00
ahtlon
d9cf3588bf
Start over but right this time
2025-01-19 14:22:08 +01:00
ahtlon
2500b8ab9a
basic discourse example
2025-01-19 14:22:08 +01:00
ahtlon
3861daaf76
[modules] move microvm module import from makeMicroVM to baseModules
2025-01-18 22:01:06 +01:00
d8d910f5fd
[uptimekuma] mv from fanny to hetzner server
...
after thinking about it it makes no sense to have status/alerting
running on fanny. as soon as fanny fails we wont get any alerts anymore.
thats why i think having it running on the hetzner server, which is
quite stable, makes sense
2025-01-17 14:19:38 +01:00
a4f6b77e30
[fanny] deploy uptimekuma
2025-01-17 14:00:41 +01:00
6aa6f2e171
[uptimekuma] set redirects
2025-01-17 13:59:54 +01:00
d9bb933891
[uptimekuma] init
2025-01-17 13:59:35 +01:00
168d45ed8a
[vpn] set mtu 1340
2025-01-17 00:29:11 +01:00
2f477d3566
[fanny] undo proxy settings
2025-01-17 00:19:23 +01:00
b40cb40b01
[fanny] try fix incomplete file transfer
2025-01-16 19:30:49 +01:00
b15b2ae789
[fanny] disable proxy_buffer
2025-01-16 16:36:38 +01:00
c7b02b9366
[vpn] disable proxy_buffer
...
url http://10.100.0.101:80/css/variables.css only returns half the file
hopefully this fixes it
2025-01-16 16:26:23 +01:00
c78eb9cbc1
[fanny][vpn] open port 80, enable nginx
2025-01-16 14:24:19 +01:00
429be2c7b9
[fanny] setup as microvm host
2025-01-16 13:17:50 +01:00
a12ad8db31
[fanny] setup proxypass chain
2025-01-16 13:17:50 +01:00
ea99bbde25
[infradocs] init
2025-01-16 13:17:50 +01:00
8e8ddb1435
[vpn] fix persistentKeepalive
2025-01-14 21:37:17 +01:00
50a506d1c2
[bakunin] fix disk id
2025-01-14 17:56:39 +01:00
3bc69085b3
[bakunin] use disko module
2025-01-14 17:53:58 +01:00
3b6107c13d
[fanny] set persistentKeepalive
...
to be able to ssh even if fanny was not active for a while
2025-01-14 16:47:08 +01:00
aaf1e280fc
[vpn] enable ip_forward on servers
2025-01-14 15:40:22 +01:00
c6c7fe5a57
[vpn] allow peers to communicate within subnet
2025-01-14 15:14:58 +01:00
60221f474c
[vpn] fix allowedIps
...
it seems allowedIPs need to have /32 subnet
2025-01-14 15:04:49 +01:00
9b526906c0
[vpn] fix allowedIPs in peers.nix
2025-01-14 14:38:09 +01:00
642bb8ba64
[fanny] fix vpn name
2025-01-14 13:53:20 +01:00
468c3d63f9
[fanny] add to malovpn
2025-01-14 13:45:53 +01:00
