No edit summary |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 13: | Line 13: | ||
* https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/howto-server-delegation.md | * https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/howto-server-delegation.md | ||
r3boot: I would prefer a lean&mean setup. So probably something like synapse, an irc bridge, some web-based client and a bot (matrix client for harkbot?), combined with LDAP auth. | |||
= Setup = | = Setup = | ||
| Line 27: | Line 28: | ||
== File Storage == | == File Storage == | ||
* We could consider using Minio for storage. If we set up a Minio instance, we can also use it for Mastodon (e.g., think s3.nurd.space). | * We could consider using Minio for storage. If we set up a Minio instance, we can also use it for Mastodon (e.g., think s3.nurd.space). | ||
Folkert: maybe some other S3 emulator? because minio is closed source | |||
== Bridges == | == Bridges == | ||
Latest revision as of 22:30, 4 October 2024
We want to set up our own Matrix home server at the space. Currently, we are still in the stage of gathering information and preparing for deployment. A start has been made a while back by Folkert, Container 119 (matrix) on node 'erratic'
Another question is how we want to properly set this up, for example. Do we want to run it in a VM, LXC and do we want to split the different services into docker containers or not?
Melan: I personally use matrix-docker-ansible-deploy because it simplifies the deployment of a “Matrix stack.” However, for the space, we might want more control over how things are deployed. It does however provide some useful documentation.
Some important documentation is;
- https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-dns.md
- https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/howto-server-delegation.md
r3boot: I would prefer a lean&mean setup. So probably something like synapse, an irc bridge, some web-based client and a bot (matrix client for harkbot?), combined with LDAP auth.
Setup
Homeserver
- Synapse: GitHub Repository
- Using PostgreSQL as the database.
- For LDAP integration, we can either use matrix-synapse-ldap3 or ma1sd (which offers more fully-featured integration).
- Administration: synapse-admin
Clients
- Element: GitHub Repository (Probably the best one there is)
File Storage
- We could consider using Minio for storage. If we set up a Minio instance, we can also use it for Mastodon (e.g., think s3.nurd.space).
Folkert: maybe some other S3 emulator? because minio is closed source
Bridges
- Heisenbridge (IRC bridge)
- matrix-hookshot (Could be useful for webhooks?)
- email2matrix (Perhaps we could use this for the mailing list.)
For the following two bridges, we’ll need to determine if we can bridge the existing NURDspace groups. There’s also the question of whether we want to direct those groups to IRC. If we do, should we push them to the #nurds channel, or perhaps create a #nurds-social channel instead?
Bots
It might be interesting/fun to port some of NURDbot's functionality over to Matrix as well.
- Mjolnir Might be useful, has to be looked into if we need it.
Other
- Coturn could be nice if we want to enable audio/video calls via Matrix.