fix mautrix-telegram

This commit is contained in:
Rouven Seifert 2025-05-01 20:20:28 +02:00
parent 7e2ec684ba
commit ff44839229

View file

@ -1,9 +1,6 @@
{ config, lib, pkgs, ... }:
let
homeserverDomain = config.services.matrix-synapse.settings.server_name;
registrationFileSynapse = "/var/lib/matrix-synapse/telegram-registration.yaml";
registrationFileMautrix = "/var/lib/mautrix-telegram/telegram-registration.yaml";
settingsFile = builtins.head (builtins.match ".*--config='(.*)' \\\\.*" config.systemd.services.mautrix-telegram.preStart);
in
{
services.postgresql = {
@ -20,23 +17,11 @@ in
owner = config.systemd.services.matrix-synapse.serviceConfig.User;
};
services.matrix-synapse.settings.app_service_config_files = [
# The registration file is automatically generated after starting the
# appservice for the first time.
registrationFileSynapse
];
systemd.tmpfiles.rules = [
# copy registration file over to synapse
"C ${registrationFileSynapse} - - - - ${registrationFileMautrix}"
"Z /var/lib/matrix-synapse/ - matrix-synapse matrix-synapse - -"
];
services.mautrix-telegram = {
enable = true;
environmentFile = config.age.secrets.mautrix-telegram.path;
registerToSynapse = true;
settings = {
homeserver = {
@ -60,15 +45,5 @@ in
};
};
};
# If we don't explicitly set {a,h}s_token, mautrix-telegram will try to read them from the registrationFile
# and write them to the settingsFile in /nix/store, which obviously fails.
# systemd.services.mautrix-telegram.serviceConfig.ExecStart =
# lib.mkForce (pkgs.writeShellScript "start" ''
# export MAUTRIX_TELEGRAM_APPSERVICE_AS_TOKEN=$(grep as_token ${registrationFileMautrix} | cut -d' ' -f2-)
# export MAUTRIX_TELEGRAM_APPSERVICE_HS_TOKEN=$(grep hs_token ${registrationFileMautrix} | cut -d' ' -f2-)
# ${pkgs.mautrix-telegram}/bin/mautrix-telegram --config='${settingsFile}'
# '');
}