trigger nixops from panel
Alright, please add this as an in-code comment so we don't lose track of it.
fix: NixOS deployment code
Apparently not, the default is 127.0.0.1
and that works, why wouldn't it?
trigger nixops from panel
I've seen this comment Fediversity/Fediversity#190 (comment)
Do we strictly require that already merely to conclude the user story this implements? If…
trigger nixops from panel
Why do we need the user here? In any case we can get it from the request context.
trigger nixops from panel
Instead of polluting business logic with a conditional dealing with inessential details, let's instead set REPO_DIR
in the devhell.
fix: NixOS deployment code
fricklerhandwerk
deleted branch fix-manage from fricklerhandwerk/Fediversity
2025-03-18 18:25:11 +01:00
fix: run `manage` in service directory
fricklerhandwerk
created branch fix-packaging in fricklerhandwerk/Fediversity
2025-03-18 18:23:55 +01:00
fix: run
manage
in service directory
fricklerhandwerk
created branch fix-manage in fricklerhandwerk/Fediversity
2025-03-18 17:50:22 +01:00
fricklerhandwerk
deleted branch update-hostkey from fricklerhandwerk/Fediversity
2025-03-18 09:51:31 +01:00
update fedi201 host public key