Conversation
|
Added a nixos test and configured it as a passthru test. I think feature-wise this is as far as I would go in this iteration. No certificate handling. |
7c93558 to
7755b85
Compare
|
And pushed an update for botamusique that allows setting the bandwidth to something more reasonable than 200 kbit/s. |
34a7487 to
96b9635
Compare
|
Updated to the latest version, that disables fetching the changelog, when autoupdates are disabled. This allows me to drop the patch I applied to the package in the nixos test.
|
There was a problem hiding this comment.
Do you mind expanding this description, usually nice to give a concise description of the package and what enabling the service does
| enable = mkEnableOption "botamusique"; | |
| enable = mkEnableOption "Enable botamusique service to play youtube or sound on mumble."; |
There was a problem hiding this comment.
That is redundant: https://github.com/NixOS/nixpkgs/blob/master/lib/options.nix#L92-L99
Usually you just pass the service name to mkEnableOption
There was a problem hiding this comment.
Oh didn't realize that it constructed the description. sorry!
Motivation for this change
Proper setup of botamusique, a mumble music bot.
I did look into certificate creation, the upstreams example looks like this:
Something users could do themselves, or we could handle it in ExecStartPre, not sure.
I did not look into what giving the bot tokens would do, I guess allow them to register?
Both could be exposed at the top-level, certificate is actually a path, tokens are literal strings. Nothing really security-critical ig.
Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)nix path-info -Sbefore and after)