This would cause emails being sent, but Synapse responding with a 429 when creating the event. The client would then retry, and with bad timing the same scenario would happen again. Some testing I did ended up sending me 10 emails for one single invite because of this.

... to help people escape env var hell

There's not much point in binding to localhost when it's in a docker container.

This is mostly a documentation change, but also adds a default value for
SYNAPSE_CONFIG_PATH, so that running from the generated config is the default,
and will Just Work provided your config is in the right place.

* Fix JWT login with register

Signed-off-by: Pau Rodriguez-Estivill <prodrigestivill@gmail.com>

* Add pyjwt conditional dependency

Signed-off-by: Pau Rodriguez-Estivill <prodrigestivill@gmail.com>

* Added changelog file

Signed-off-by: Pau Rodriguez-Estivill <prodrigestivill@gmail.com>

* Improved changelog description

Signed-off-by: Pau Rodriguez-Estivill <prodrigestivill@gmail.com>

Docker: generate our own log config

this makes docker builds a bit faster.

Docker image: add support for SYNAPSE_DATA_DIR parameter

Docker: only run --generate-keys when generating config on-the-fly.

Refactor the docker/start.py script

Update purge_api README

Update HAProxy example rules

Signed-off-by: Jon Richter <jon@allmende.io>

This points the reverse links at the intended location.

When running under docker, we want to use docker's own logging stuff rather
than losing the logs somewhere on the container's filesystem, so let's use log
configs that spit logs out to stdout instead.

Fixes #4830.

We don't want to generate any missing configs when running from a precanned
config.

(There's a strong argument that we don't want to do this at all, since
generating a new signing key on each invocation sounds disasterous, but I don't
fancy unpicking that for now.)

Fixes #4901

* master:
  Fix broken link in MSC1711 FAQ
  Update changelog to better expain password reset change (#5545)

* release-v1.0.0:
  Update changelog to better expain password reset change (#5545)

... and inline generate_secrets

Closes #4583

Does slightly less than #5045, which prevented a room from being upgraded multiple times, one after another. This PR still allows that, but just prevents two from happening at the same time.

Mostly just to mitigate the fact that servers are slow and it can take a moment for the room upgrade to actually complete. We don't want people sending another request to upgrade the room when really they just thought the first didn't go through.

Fixes #3370.