3 ms·
I haven't written anything up anywhere, but I have a rough outline of it - I can pull it together today and see if it's consumable by others. If you're at all f
by abstract_put 6y ago
I haven't written anything up anywhere, but I have a rough outline of it - I can pull it together today and see if it's consumable by others. If you're at all familiar with the tools, they're deployed in their most vanilla capacities. The grief for me was the tiny amount of configuration each piece needed to fit with everything else. Components: postgres, Synapse (Matrix server), Signald (Signal client daemon), mautrix-signal (Signal-Matrix bridge), mautrix-whatsapp (WhatsApp-Matrix bridge), Element (Matrix client)
- dunefox 6y ago> I can pull it together today and see if it's consumable by others. That would be great since I have no idea at all.
- abstract_put 6y agoI didn't get around to actually doing something nice, but rather than leave things hanging I dumped my docker-compose file + some notes (that might be mostly useless) here: https://controlc.com/fbe73ad3 https://controlc.com/fbe73ad3. When I move it to a different machine, as this was originally just out of curiosity until it worked so well, I'll make sure to write something more usable up. It's been ~6 weeks since I set it up and it's been working since the first time without any modifications, so I honestly forget some of what I did. The general flow is: configure the bridges (config.yaml), integrate them with Synapse (registration.yaml), add your Matrix user, then configure the bridge users.