35

Hi all,

I want to host my own matrix server, so that i can run bridges to all the other (stupid) messaging apps.

I am looking for any advice or experience in choosing which server to run, and if you know of any good tutorials, run throughs, etc. i typically would like a lighter instance, as i expect about 3 users, with 2 of us needing bridging.

  • dendrite
  • synapse
  • conduit
  • construct

and then the addition of bridges, (Signal, WA, Messenger and hopefully SMS).

I am fairly self sufficient when it comes to self hosting, and i run everything on linux, in docker, proxied by Nginx proxy manager. but typically prefer stuff that works more or less out of the box.

Thanks all!

you are viewing a single comment's thread
view the rest of the comments
[-] SJ0@lemmy.fbxl.net 1 points 1 year ago* (last edited 1 year ago)

My experience has been that dendrite and synapse totally maxxed out the server I ran it on (100% cpu utilization for days on end), so I run conduit.

The one downside of conduit is it's a bit behind, so it doesn't support all the latest rooms, and it doesn't support spaces yet, and it has minimal admin tools so you'll want to create all the accounts you need then close logins because bad actors will try to create logins and get you banned from half of Matrix. That said, I can tell you that even on my piddly little server (an Intel Atom D2550), it runs Conduit, ejabberd, nostr, and lotide, and the server basically sits idle. I can't speak of bridges, unfortunately, because I don't really use them.

This is the guide I used, it worked well to set things up:

https://gitlab.com/famedly/conduit/-/blob/next/DEPLOY.md

[-] palitu@lemmy.perthchat.org 2 points 1 year ago

thanks - the dendrite and synapse experience is what i am worried about - it seems to be the massive implementation that will scale to millions.

i was looking at conduit, but realy dont know what the issues i will come against with it. but it seems to be the most visible of the non-major implementations.

[-] SJ0@lemmy.fbxl.net 1 points 1 year ago* (last edited 1 year ago)

Besides lacking spaces and some rooms not letting you join, (and the lack of admin tools) the only big issue I find is that you plan to run something other than Element as the interface, you'll have to test it because many matrix clients expect synapse or dendrite and won't start with anything else. I've run fluffychat, I think kchat(whatever the kde matrix client is), and nheko, they all worked well with conduit.

[-] palitu@lemmy.perthchat.org 2 points 1 year ago

as you saying that element doesn't work?

[-] SJ0@lemmy.fbxl.net 1 points 1 year ago

No, I'm saying it does work, but other clients might not.

[-] palitu@lemmy.perthchat.org 2 points 1 year ago

ah, yep - that is cool. I expect that i will use Element and potentially another simpler client.

I am also curious about how element X will go, which requires the sliding API/proxy thingo. but that is future palitu's problem.

this post was submitted on 24 Jul 2023
35 points (100.0% liked)

Selfhosted

40394 readers
333 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS