[huxflux]

I've been setting up servers for everything ranging from IRC to Teamspeak, Exchange, and you name it. But how come setting up a Matrix server is still a science in itself?

Yes, I'm aware of the Ansible script, but should that really be the only somewhat reasonable option? When Matrix wrote " Matrix 2.0 a new chance if you gave up on us in the past".

I listened, but without a somewhat reasonable setup process for the server and the ongoing confusion in terms of clients, it hasn't gotten any easier to onboard to Matrix, unfortunately.

[NicolaiS]

Self-hosting Conduit as my homeserver using SQLite as by database and Caddy as reverse proxy.

That is: 2 binaries (conduit + caddy) + 5 lines of toml config for Conduit and 2 line of config for Caddy + 1 database file. That's all you need for a basic homeserver.

[factormeta]

just wonder what is wrong with the default rocksdb setup that came with Conduit? Wouldn't that be better for concurrencies?

[xinayder]

I have to agree with you. Not having a proper, understandable documentation is part of what drives people away from Matrix, IMO.

And shoving the ansible script into people's faces is not a solution. I never used Ansible, and I won't start using it just because it's "easier" to setup Matrix with it, instead of setting it up by myself.

All services I self-host are quite easy to setup, Matrix so far has been a bit more difficult, but not that hard.

[Arathorn]

this is literally why i wrote https://github.com/element-hq/element-docker-demo

[Arathorn]

i think you're asking for https://element.io/blog/experimenting-with-matrix-2-0-using-...