15
submitted 1 year ago* (last edited 1 year ago) by thisisawayoflife@lemmy.world to c/selfhosted@lemmy.world

How does this work? How do you host pixelfed.domain.com and mastodon.domain.com together in the same domain, with queries for "@user@domain.com" to the webfinger host path?

I'm other words, how does the querying application know which resource it needs? How do you know that a pixelfed instance will get the pixelfed resource versus the mastodon resource?

all 7 comments
sorted by: hot top controversial new old
[-] simon@lemmy.utveckla.re 4 points 1 year ago

The webfinger includes the subdomain. So the webfinger would be either @user@mastodon.domain.com or @user@pixelfed.domain.com, given your example.

[-] thisisawayoflife@lemmy.world 3 points 1 year ago

Does it still work that way when using the web_domain setting?

https://docs.joinmastodon.org/admin/config/#web_domain

[-] festus@lemmy.ca 2 points 1 year ago

I can't speak for those two services in particular, but I know that Matrix will check https://domain.com/.well-known/matrix/server to see what (sub)domain is responsible for domain.com. I suspect other services also use .well-known too.

[-] thisisawayoflife@lemmy.world 1 points 1 year ago

Yes, they use a webfinger on the .well-known path.

[-] stown@sedd.it 1 points 1 year ago

I've thought that if some dev created a webfinger reverse proxy they would be the hero of the fediverse.

[-] thisisawayoflife@lemmy.world 3 points 1 year ago

I've thought about doing this. It seems simple enough, though it would need a front end to be user friendly. I could build the rest api pretty quickly.

this post was submitted on 05 Sep 2023
15 points (100.0% liked)

Selfhosted

40394 readers
388 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS