-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Docker image no longer starts if you set SYNAPSE_SMTP_HOST #5430
Comments
The workarounds for now are either:
|
A quick fix before figuring out the whole Docker mess is just to add a But we should really figure this out :/ |
I'm not convinced adding a We're going to be telling people to switch to the The only question is whether we can do something better for people whose working configs have been broken by 1.0, like disabling password resets altogether? Given the |
(incidentally it might be good to do that against the release branch and we can update the docker image on dockerhub.) |
This sounds best to me, considering, as you say, they were never actually used. |
Because of #5518, I believe we can say "use a proper config" here, and close it? |
As per #5430 (comment): I'd prefer not to break peoples' working configs, and I think we can do better. |
The |
Removes any `SMTP_*` docker container environment variables from having any effect on the default config. Fixes #5430
the readme will be updated at the same time as the docker image is updated on hub.docker. fixed by #5596 |
As far as I can tell, the
SYNAPSE_SMTP_*
settings were never used, becauseemail_notifs
was set tofalse
in thehomeserver.yaml
used by the docker image. Nevertheless the documentation kinda encourages you to set theSYNAPSE_SMTP_*
settings. Those that did so will now find that their servers refuse to start, with:The text was updated successfully, but these errors were encountered: