Selfhosted

39246 readers

325 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

Self hosting matrix is great! (feddit.de)

submitted 1 year ago by [email protected] to c/selfhosted

35 comments fedilink hide all child comments

I just set it up today. The docker setup was pretty easy and I got the telegram and WhatsApp bridge running so I have all my messages in one place. Signal bridge is next.

Is anyone else doing this?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

Here is my compose file:

version: '3.3'

services:
  app:
    image: matrixdotorg/synapse
    restart: unless-stopped
    ports:
      - 8008:8008
    volumes:
      - ./data:/data
    hostname: matrix

  mautrix-telegram:
    container_name: mautrix-telegram
    image: dock.mau.dev/mautrix/telegram
    restart: unless-stopped
    volumes:
      - ./mautrix-telegram-data:/data
    hostname: mautrix-telegram

  mautrix-whatsapp:
    container_name: mautrix-whatsapp
    image: dock.mau.dev/mautrix/whatsapp
    restart: unless-stopped
    volumes:
      - ./mautrix-whatsapp-data:/data
    hostname: mautrix-whatsapp

I have nginx running as a reverse proxy on the host. I haven't gotten the federation to work yet but I think it's an ipv6 issue.

Setting up the bridges was quiet easy using these instructions

Let me know if you have anymore questions. It's running on a small host with 40 docker containers running in parallel and the cpu sits idle at 5% so it's not much of a drain.