forked-synapse/changelog.d/4052.feature

Ship the example email templates as part of the package

**Note**: if you deploy your Synapse instance from a git checkout or a github
snapshot URL, then this means that the example email templates will no longer
be installed in `res/templates`. If you have email notifications enabled, you
should ensure that `email.template_dir` is either configured to point at a
directory where you have installed customised templates, or leave it unset to
use the default templates.

The configuration parser will try to detect the situation where
`email.template_dir` is incorrectly set to `res/templates` and do the right
thing, but will warn about this.
Ship the email templates as package_data move the example email templates into the synapse package so that they can be used as package data, which should mean that all of the packaging mechanisms (pip, docker, debian, arch, etc) should now come with the example templates. In order to grandfather in people who relied on the templates being in the old place, check for that situation and fall back to using the defaults if the templates directory does not exist. 2018-10-17 14:44:34 +00:00			`Ship the example email templates as part of the package`

			`Note: if you deploy your Synapse instance from a git checkout or a github`
			`snapshot URL, then this means that the example email templates will no longer`
			be installed in `res/templates`. If you have email notifications enabled, you
			should ensure that `email.template_dir` is either configured to point at a
			`directory where you have installed customised templates, or leave it unset to`
			`use the default templates.`

			`The configuration parser will try to detect the situation where`
			`email.template_dir` is incorrectly set to `res/templates` and do the right
			`thing, but will warn about this.`