With “support for them” I meant if this only applies to the host with the exporter or also to cthuga (which is a debian machine right?)
Does the current Debian release supports the…
does cthugha needs support for them? Because if not 1.) is not the right constraint for nix machines.
Maybe we should rethink this list. Even if we end up with the same list, but a less
This is the closing bracket of the services record, there should be less white space, right?
I don't know much about prometheus and which options should be set and which not. I would love if @dsimon could leave a comment here about that.
Before merging, we should look through the list of exporters and choose the ones we like. CC @dsimon
If we want to start a discussion we should open.an issue
isn't this handled by services.jitsi-videobridge.openFirewall = true; If it is, I would not want to have that again explicitly. (or at least a comment why we want to set it explicitly again). (Or maybe I'm wrong)
We probably want additional persistence of /var/lib/jisti-meet and /var/lib/prosody
jitsi.nix does not use flake-inputs ever, why not scratch that parameter from the module and don't apply it here