19 Commits

Author	SHA1	Message	Date
kalipso	68b3da7df8	[fanny] proxypass cloud.malobeo.org	2025-01-19 14:53:39 +01:00
kalipso	affcc71eb1	[fanny] deploy nextcloud	2025-01-19 14:52:33 +01:00
kalipso	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
kalipso	a4f6b77e30	[fanny] deploy uptimekuma	2025-01-17 14:00:41 +01:00
kalipso	6aa6f2e171	[uptimekuma] set redirects	2025-01-17 13:59:54 +01:00
kalipso	2f477d3566	[fanny] undo proxy settings	2025-01-17 00:19:23 +01:00
kalipso	b40cb40b01	[fanny] try fix incomplete file transfer	2025-01-16 19:30:49 +01:00
kalipso	b15b2ae789	[fanny] disable proxy_buffer	2025-01-16 16:36:38 +01:00
kalipso	c78eb9cbc1	[fanny][vpn] open port 80, enable nginx	2025-01-16 14:24:19 +01:00
kalipso	429be2c7b9	[fanny] setup as microvm host	2025-01-16 13:17:50 +01:00
kalipso	a12ad8db31	[fanny] setup proxypass chain	2025-01-16 13:17:50 +01:00
kalipso	642bb8ba64	[fanny] fix vpn name	2025-01-14 13:53:20 +01:00
kalipso	468c3d63f9	[fanny] add to malovpn	2025-01-14 13:45:53 +01:00
kalipso	f0e7fef90e	[fanny] add to sops	2025-01-14 13:45:34 +01:00
ahtlon	a5d6cd6455	Configure fanny for disk and initssh module	2025-01-05 20:46:37 +01:00
ahtlon	b0a5fd91cd	fix my mistakes	2024-12-31 03:18:37 +01:00
kalipso	fedf849499	[fanny] set neededForBoot flags	2024-12-20 23:47:25 +01:00
kalipso	6932f8507a	[fanny] setup disko drive layout	2024-12-11 11:56:41 +01:00
kalipso	59e10c3eea	[fanny] init	2024-12-10 17:27:14 +01:00