Matrix-WhatsApp Bridge with Docker

[oj]

Couldn't this Docker App be packaged as an App on Cloudron...and networked with the Cloudron Synapse Server app?

It would essentially be one big part of the new "Element One" offering from Element Matrix Services.

https://docs.mau.fi/bridges/go/whatsapp/setup/docker.html#whatsapp-bridge-setup-with-docker

https://github.com/mautrix/docs/blob/master/bridges/go/whatsapp/setup/docker.md

[r369]

Please @appdev can you deploy the Whatsapp bridge and Telegram bridge.

I am more than happy to pay to an individual for a deployment to the current matrix.
@girish @nebulon @BrutalBirdie

[krumel]

Generally speaking a integration of the more popular bridges would be really neat.
Mainly thinking about these:

• Signal
• WhatsApp
• SMS
• E-Mail
• FB Messenger
• Slack
• Discord
• IRC
• Telegram
• WeChat

Especially in the light of Bot and AI integration that could be a really game changer and really bring matrix deployment forward.
And as matrix deployment is a reason for a lot of people to use cloudron (as it is a pain in the bottom otherwise) it might even be financially profitable for you guys to do so - I know a few people who stick with yuno because the lack of bridges on cloudron.

[subven]

I have bridgebots (mautrix) running on a small 2€ per month VPS and use Cloudrons Matrix + Element. Just Portainer + NGINX Proxy Manager + Mautrix bots. Works well and is really easy to setup and maintain.

Having everything at Cloudron would be a plus but as long as nobody takes the time to package these services...
Begging/Pressure the devs and team for rather niche services/apps to get packed is not the right way ^^

[krumel]

@subven

Where exactly do you see that I am begging a dev here?

I am merely adding that a lot of people are using cloudron free to circumvent the hassle of setting up matrix on their own - in fact that is a advice given quite frequently on some subreddits and the reason why I ended up here - only to become a paying customer later on. (And once they took the bait of the "working matrix" it might be easier to catch them as paying customers with the integrations?)

Sure, one could always use complete self-hosting as you described and I am very happy that it worked out for you - it didn't for a lot of other people and neither for me.
But that is the point why most people use cloudron in the end, isn't it? The ease of things?
This is in the end what most people pay for - the effortlessness cloudron provides.

(Besides: This is not a open source hobby project but something the Devs need to make a living off. So discussing what features are desireable and making sense fiscally is somewhat beneficiary for both sides, isn't it?)

Kind regards,
Phil

[carrick]

@subven - I'd love to better understand how you configured the bridges on your separate VPS. Was there anything on the Cloudron Matrix server config you needed to enable to allow the bridges to communicate? If you can share how you set any of this up I'd love to see it.

[subven]

@carrick you have to add mautrix-telegram-registration.yaml (or corresponding) to your Matrix /configs folder in Cloudron and adjust the homeserver.yaml.

app_service_config_files:
  - '/app/data/configs/mautrix-telegram-registration.yaml'

Bridge setup is rather easy as you just start the docker container and stick to the documentation. Take a look at the docker logs to identify problems with the bridge. There are many tutorials over the net on how to create a bot and hosting a bridge and I read a couple of them to get an overview + used the offical documentation. Took me 2 hours to setup everything so it should be doable ^^

For the VPS I just used OS + Docker and Nginx Proxy Manager + Portainer as containers besides the bridges.

[r369]

@subven can you please help me to setup? I am more than happy to pay for it.

[BetaBreak]

@subven - Would it be possible to share your yaml files so I could understand how to configure the network settings? Thanks!