14 Commits (da2a6682b39699d0e572a2fd5bcf0350844cd22b)

Author	SHA1	Message	Date
Slavi Pantaleev	da2a6682b3	Get rid of matrix_mautrix_signal_configuration_permissions ... While it's kind of nice having it, it's also somewhat raw and unnecessary. Having a good default and not even mentioning it seems better for most users. People who need a more exposed bridge (rare) can use override the default configuration using `matrix_mautrix_signal_configuration_extension_yaml`.	4 years ago
Slavi Pantaleev	df8d9cfd34	Remove some TODOs ... The answer to these is: it's good to have them in both places. The role defines the obvious things it depends on (not knowing what setup it will find itself into), and then `group_vars/matrix_servers` "extends" it based on everything else it knows (the homeserver being Synapse, whether or not the internal Postgres server is being used, etc.)	4 years ago
Sabine Laszakovits	89f7f3c3b8	added log level configuration	4 years ago
Sabine Laszakovits	ffb837d4bc	made the bridge use the default postgres db	4 years ago
Sabine	aabefe21f4	fixed yaml	4 years ago
Sabine Laszakovits	dd50ee19ab	fixed bridge permissions	4 years ago
Sabine Laszakovits	2211e678f3	fixed comments that were copied over from mautrix-telegram role	4 years ago
Sabine Laszakovits	e59aa07b86	more cleanup	4 years ago
Sabine Laszakovits	c36e1355cf	cleanup	4 years ago
Sabine Laszakovits	8ebc39dea0	fixed dependencies of bridge service (not ideal, but correct)	4 years ago
Sabine Laszakovits	9b890e9ced	moved some settings from role to group_vars	4 years ago
Sabine Laszakovits	ff1d7921a0	moved registration.yaml contents to template	4 years ago
Sabine	7a54e11090	started moving settings to group_vars	4 years ago
Sabine	69efcb5c21	added mautrix-signal role	4 years ago