74885a7ce1
[nix] add run-vm script
2025-01-20 02:37:19 +01:00
eafe7a6b95
[vpn] update dummy secrets
Check flake syntax / flake-check (push) Successful in 8m32s
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
015c326042
[nix] rm vm interface overwrite
Check flake syntax / flake-check (push) Failing after 6m22s
2025-01-19 23:40:15 +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
36ec5f5837
[sops] test sharing hostkey with vm
2025-01-19 22:55:52 +01:00
68b3da7df8
[fanny] proxypass cloud.malobeo.org
Check flake syntax / flake-check (push) Successful in 6m3s
2025-01-19 14:53:39 +01:00
affcc71eb1
[fanny] deploy nextcloud
Check flake syntax / flake-check (push) Has been cancelled
2025-01-19 14:52:33 +01:00
4462856fa0
[nextcloud] rm obsolete nameserver
2025-01-19 14:52:20 +01:00
5352c1fa4d
[docs] make readme the index
...
still most of it is quite out of date...
2025-01-19 14:30:58 +01:00
ahtlon
fabf48a5c0
[nextcloud] nextcloud works now
Check flake syntax / flake-check (push) Successful in 8m17s
2025-01-19 14:22:08 +01:00
ahtlon
617c177892
[nextcloud] flake update because for some reason the sha changed
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
52824e39ee
with nix flake check the hydraJobs output is evaluated in the same way as Hydra's hydra-eval-jobs
Check flake syntax / flake-check (push) Successful in 13m21s
2025-01-18 23:41:53 +01:00
ahtlon
8793120436
Only run on push
2025-01-18 23:40:11 +01:00
ahtlon
950ada1e10
[actions] Add flake check
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 4m33s
Check flake syntax / flake-check (push) Successful in 7m30s
2025-01-18 22:24:21 +01:00
ahtlon
1e269966ff
Merge branch 'fix-flake-check'
...
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 5m54s
nix flake check and show now work again
2025-01-18 22:02:19 +01:00
ahtlon
3861daaf76
[modules] move microvm module import from makeMicroVM to baseModules
2025-01-18 22:01:06 +01:00
ahtlon
3a332e77d1
[scripts] move packages to legacyPackages
2025-01-18 21:45:48 +01:00
ahtlon
79c311b45d
Merge branch 'issue51'
...
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 6m3s
Fixes #51
2025-01-18 20:41:06 +01:00
ahtlon
850070f987
[scripts] check for flake.nix
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 4m15s
2025-01-18 20:39:16 +01:00
ahtlon
d242562544
[packages] make scripts available in shell without nix run
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 4m7s
2025-01-18 20:04:22 +01:00
d8d910f5fd
[uptimekuma] mv from fanny to hetzner server
...
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 4m7s
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
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 4m21s
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
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 5m47s
2025-01-17 00:29:11 +01:00
2f477d3566
[fanny] undo proxy settings
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 4m18s
2025-01-17 00:19:23 +01:00
b40cb40b01
[fanny] try fix incomplete file transfer
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 4m5s
2025-01-16 19:30:49 +01:00
b15b2ae789
[fanny] disable proxy_buffer
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 4m2s
2025-01-16 16:36:38 +01:00
c7b02b9366
[vpn] disable proxy_buffer
...
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 4m5s
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
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 5m49s
2025-01-16 14:24:19 +01:00
429be2c7b9
[fanny] setup as microvm host
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 3m55s
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
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 3m53s
2025-01-14 21:37:17 +01:00
50a506d1c2
[bakunin] fix disk id
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 7m4s
2025-01-14 17:56:39 +01:00
3bc69085b3
[bakunin] use disko module
Evaluate Hydra Jobs / eval-hydra-jobs (push) Has been cancelled
2025-01-14 17:53:58 +01:00
3b6107c13d
[fanny] set persistentKeepalive
...
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 3m44s
to be able to ssh even if fanny was not active for a while
2025-01-14 16:47:08 +01:00
