| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Don't load the generated config as the default. | Richard van der Hoff | 2019-06-24 | 1 | -1/+1 |
| | | | | | It's too confusing. | ||||
| * | Pass config_dir_path and data_dir_path into Config.read_config. (#5522) | Richard van der Hoff | 2019-06-24 | 1 | -1/+1 |
| | | | | | | | * Pull config_dir_path and data_dir_path calculation out of read_config_files * Pass config_dir_path and data_dir_path into read_config | ||||
| * | Comment out most options in the generated config. (#4863) | Richard van der Hoff | 2019-03-19 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | | | | | Make it so that most options in the config are optional, and commented out in the generated config. The reasons this is a good thing are as follows: * If we decide that we should change the default for an option, we can do so, and only those admins that have deliberately chosen to override that option will be stuck on the old setting. * It moves us towards a point where we can get rid of the super-surprising feature of synapse where the default settings for the config come from the generated yaml. * It makes setting up a test config for unit testing an order of magnitude easier (see forthcoming PR). * It makes the generated config more consistent, and hopefully easier for users to understand. | ||||
| * | Attempt to make default config more consistent | Richard van der Hoff | 2019-02-19 | 1 | -1/+3 |
| | | | | | | | The general idea here is that config examples should just have a hash and no extraneous whitespace, both to make it easier for people who don't understand yaml, and to make the examples stand out from the comments. | ||||
| * | Flake8 | Erik Johnston | 2017-10-19 | 1 | -4/+0 |
| | | |||||
| * | Add missing file... | Erik Johnston | 2017-10-19 | 1 | -0/+36 |
 |
index : matrix/thirdparty/synapse.git | |
| Unnamed repository; edit this file 'description' to name the repository. |
| summary refs log tree commit diff |