I’m interested in setting up my own instances for Lemmy, Mastodon, and Matrix.
Can I use the same https://domain.tld for all of them without any subdomains?
For example:
lemmyuser@mydomain.tld
mastodonuser@mydomain.tld
matrixuser@mydomain.tld
Will this work across all of my self-hosted instances, or do I need to append a subdomain for each, e.g., lemmyuser@lemmy.mydomain.tld?
All those services use a protocol named WebFinger that allows for having the servers in different domains but showing the users as being in a main domain. For example, my self-hosted Synapse server is at matrix.domain.tld, but my users are all like user@domain.tld.
Unfortunately I don’t really know how to set it all up manually, I just let Yumohost take care of managing it.
Matrix (or even easier XMPP) can coexist on the same domain with Lemmy or Mastodon, but with two ActivityPub services that is AFAIK not possible.
Regardless of configuration, you still need to access the instance from mastodon.mydomain.tld or lemmy.mydomain.tld, but you can configure the Mastodon to use @mastodonuser@mydomain.tld as its identifier by setting
WEB_DOMAINtomydomain.tld.Mastodon documentation on the topic: https://docs.joinmastodon.org/admin/config/#web_domain
You are able to host all these services and more on the same domain. I do a similar thing with different services at different subdomains. I don’t believe the
username@portion can help point to different services, that syntax is usually associated with email addresses.I think the best way to go about it would be having different subdomains such as
lemmy.domain.tld,matrix.domain.tld, etc.
To accomplish that, I have a wildcard subdomain point to my server, my reverse proxy (Caddy) handles figuring out which subdomain maps to which service on top of handling TLS certificates for me.Good to know and I was hoping that’s the case. As soon as my new domain resolves I’m going to install lemmy, matrix, and funkwhale.
Are you running all of yours in containers?
All of my services are in containers, I use Docker usually via Docker Compose. That gives me one file to establish all of my services, update/start/stop/check logs with consistent command formats for all services, and keeps the data separate from the application. If I need to rebuild, put a backup of my data in the right spot and change names in filepaths as needed, run a backup of the Docker Compose file and I’m up and running again.
The only things I don’t have in a container is Fail2Ban on my rented, public facing server to minimize noise of bots trying to login.
