-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nixos/mautrix-telegram: doc update and cleanup #201560
Conversation
pacien
commented
Nov 16, 2022
- nixos/mautrix-telegram: add documentation for setting arbitrary secrets
- Revert "nixos/mautrix-telegram: substitute secrets in config file at runtime (nixos/mautrix-telegram: substitute secrets in config file at runtime #112966)"
- nixos/mautrix-telegram: document JSON env var config
The change that allows setting the secrets by an environment file had the undocumented side effect of allowing to set any key by the environment file (Related PR: mautrix/telegram#332). This is required to e.g. set `bridge.login_shared_secret`, which was not documented before. GitHub: closes NixOS#103347
…runtime (NixOS#112966)" This is no longer necessary since mautrix-telegram v0.12.1, which supports JSON-formatted environment variable and therefore maps natively. See: mautrix/telegram#584 (comment) See: https://github.com/mautrix/telegram/releases/tag/v0.12.1 This partially reverts commit 24133ea.
This was introduced in mautrix-telegram v0.12.1. See: mautrix/telegram#584 (comment) See: https://github.com/mautrix/telegram/releases/tag/v0.12.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code changes only revert the nix-specific substitution method, so this will be fine. Everything else relies on (new) upstream features, so there is not much that can break. I currently don't have time to test the code.
The upstream documentation does not seem to have anything about json::
substitutions, but the author of the bridge describes the format here (also linked in the commit messages).
Assuming that @pacien likely tested this modification, I think it is ready to merge.
Quoting Carl Richard Theodor Schneider (2022-11-20 21:19:11)
Assuming that @pacien likely tested this modification, I think it is
ready to merge.
Yes, I forgot to mention that ; I'm currently running the proposed
changes locally successfully.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
(Out of curiosity, where did the first commit by @CRTified come from? e.g. I don't see another PR it was taken from.) |
And for completeness: My PR got closed as an automatic action in the commit message from 6070b99. |
This did not work for me at all, see mautrix/telegram#584 (comment). |