mattermost: don't read config from database

apparently the nixpkgs mattermost module simply ignores its own config
if mutableConfig is false, and reads whatever config is currently in the
database (in our case, old stuff involving auth.infra4future.de).

This overwrites that.
This commit is contained in:
stuebinm 2022-10-16 14:32:04 +02:00
parent 52f9f2d64c
commit f64b1f9534
No known key found for this signature in database
GPG key ID: 695C841098BECF1D

View file

@ -36,6 +36,9 @@ in {
systemd.services.mattermost.serviceConfig.EnvironmentFile = systemd.services.mattermost.serviceConfig.EnvironmentFile =
"/persist/mattermost/secrets.env"; "/persist/mattermost/secrets.env";
# overwrite the -c flag given in the module. this can be removed once we're on nixos 22.05
systemd.services.mattermost.serviceConfig.ExecStart =
lib.mkForce "${pkgs.mattermost}/bin/mattermost -c /persist/mattermost/config/config.json";
# couldn't figure out how to actually overwrite modules, so now # couldn't figure out how to actually overwrite modules, so now
# there's two mattermost modules ... # there's two mattermost modules ...
@ -125,7 +128,7 @@ in {
EnableSMTPAuth = true; EnableSMTPAuth = true;
SMTPUsername = "noreply@infra4future.de"; SMTPUsername = "noreply@infra4future.de";
SMTPServer = "mail.hacc.space"; SMTPServer = "mail.hacc.space";
SMTPPort = 465; SMTPPort = "465";
SMTPServerTimeout = 10; SMTPServerTimeout = 10;
ConnectionSecurity = "TLS"; ConnectionSecurity = "TLS";
}; };