finallycoffee/matrix-docker-ansible-deploy
5
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Get rid of matrix_mautrix_signal_configuration_permissions

Browse Source 
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`.
This commit is contained in:
Slavi Pantaleev
2021-01-03 08:06:32 +02:00
parent aac400664a
commit da2a6682b3
4 changed files with 3 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/configuring-playbook-bridge-mautrix-signal.md
View File

@ -12,24 +12,6 @@ Use the following playbook configuration:
matrix_mautrix_signal_enabled: true
```
To specify which users have access to the bridge, use the variable `matrix_mautrix_signal_configuration_permissions`.
Refer to the documentation for
```yaml
bridge:
permissions:
```
in [the example config in mautrix-signal](https://github.com/tulir/mautrix-signal/blob/master/mautrix_signal/example-config.yaml).
For instance, use
```yaml
matrix_mautrix_signal_configuration_permissions: |
{
'{{ matrix_domain }}': 'user'
}
```
to allow all users registered to the current host's matrix domain access to the bridge, or hard-code whatever you like.
(See [this issue](https://github.com/ansible/ansible/issues/17324#issuecomment-449642731) on how to use variable names as dictionary keys.)
## Set up Double Puppeting
If you'd like to use [Double Puppeting](https://github.com/tulir/mautrix-whatsapp/wiki/Authentication#replacing-whatsapp-accounts-matrix-puppet-with-matrix-account) (hint: you most likely do), you have 2 ways of going about it.