this post was submitted on 16 Jun 2023
4 points (100.0% liked)

Self Hosted - Self-hosting your services.

14471 readers
17 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

Important

Cross-posting

If you see a rule-breaker please DM the mods!

founded 4 years ago
MODERATORS
 

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:
[email protected]
[email protected]
[email protected]

Will this work across all of my self-hosted instances, or do I need to append a subdomain for each, e.g., [email protected]?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 2 years ago (2 children)

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.

[–] [email protected] 0 points 2 years ago* (last edited 2 years ago) (1 children)

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?

[–] [email protected] 1 points 2 years ago

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.