Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add function to load config without generating it | Mark Haines | 2016-06-09 | 1 | -2/+20 |
| | | | | | | | | | | | | | | | | Renames ``load_config`` to ``load_or_generate_config`` Adds a method called ``load_config`` that just loads the config. The main synapse.app.homeserver will continue to use ``load_or_generate_config`` to retain backwards compat. However new worker processes can use ``load_config`` to load the config avoiding some of the cruft needed to generate the config. As the new ``load_config`` method is expected to be used by new configs it removes support for the legacy commandline overrides that ``load_or_generate_config`` supports | ||||
* | Check that the disable_registration config key is handled correctly | Mark Haines | 2016-02-22 | 1 | -0/+21 |
| | |||||
* | Typo | Erik Johnston | 2016-02-09 | 1 | -1/+1 |
| | |||||
* | Fix test | Erik Johnston | 2016-02-09 | 1 | -3/+4 |
| | |||||
* | Error if macaroon key is missing from config | Daniel Wagner-Hall | 2016-02-05 | 1 | -0/+77 |
Currently we store all access tokens in the DB, and fall back to that check if we can't validate the macaroon, so our fallback works here, but for guests, their macaroons don't get persisted, so we don't get to find them in the database. Each restart, we generate a new ephemeral key, so guests lose access after each server restart. I tried to fix up the config stuff to be less insane, but gave up, so instead I bolt on yet another piece of custom one-off insanity. Also, add some basic tests for config generation and loading. |