29
Self-hosting a Matrix server for 5 years (yaky.dev)
submitted 8 months ago by to c/selfhosting@slrpnk.net
7 comments fedilink hide all child comments
 

Experiences with the Matrix protocol, Matrix Synapse server, bridges, and Element mobile app. There are some you-just-have-to-know-this issues.

TL;DR:

  • Matrix Synapse: works fine, but requires constant manual maintenance.
  • Bridges: work pretty well.
  • Element: generally OK, some issues with timely notifications, no feature parity between Element Classic and Element X, terrible on-boarding (with current setup)
you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 8 months ago (1 child)

I'm curious what maintenance you need to do each month, I've been running matrix for well over 5 years and I haven't done anything other the keep the docker/db containers updated.

Should I have been doing stuff? Now I'm worried.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 6 points 8 months ago (1 child)

    For me, it was not monthly, but rather "when it bites you in the ass".

    • Delete all empty rooms and federated rooms without local users.
    • Clean up state_groups_state table.
    • Delete old media.

    All of this is made worse by having more active users and made better by having a large hard drive (my VPS had 20GB, which I almost filled up with the db and media after a few years, with only few users)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 8 months ago

    Ah, makes perfect sense, I don't use the federation and I've got all media on a NAS with 24TB of space, so I've not really been concerned with space usage... I might want to do some house keeping at some point though.

    Glad I hadn't missed any major.

    Thanks for the reply.

  • permalink
  • fedilink
  • source
  • parent