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

Lemmy Support

4660 readers
19 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
 

Is it possible, or will it be possible eventually, to delegate your Lemmy instance to a different URL?

For example, if I wanted to setup my own self-hosted instance at example.com, so that my username would be @[email protected], would it then be possible to host the actual Lemmy installation at example.com/lemmy/, leaving the main domain example.com available for me to host whatever I want?

I would love to setup my own instance with a nice short domain, instead of something like @[email protected], but without being able to delegate you essentially have to sacrifice the whole domain to the Lemmy installation, which is something I don't really want to do with a short domain.

What came to mind is OpenID, where using the example above, you could use example.com to sign-in to any site that supported OpenID, and then on example.com you would have a link to the actual OpenID provider in the code somewhere, and everything just worked.

top 2 comments
sorted by: hot top controversial new old
[โ€“] Mstraa 1 points 1 year ago (1 children)

You can use a sub domain like : a.example.com. You can look at the sh.itjust.works lemmy server and at the main domain : itjust.works.

Well it doesn't work anymore because the instance master made a redirection, but previously it was another site on the shorter URL.

[โ€“] [email protected] 1 points 1 year ago

I've already investigated using a subdomain, and it may have to be the way I go for now, but it's not really ideal. @[email protected] is much nicer and easier to remember and give out than @[email protected] or @[email protected].

Plus I'm (hopefully) foreseeing a future of running multiple federated apps that allow delegation, so if I wanted to have a Lemmy instance, a Matrix instance, and a Mastadon instance, if they all eventually allow delegation I can give everyone @[email protected] for literally any of my federated services, instead of @[email protected], @[email protected], etc.