Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sharing a vanity domain with wildebeest #65

Open
xortive opened this issue Jan 10, 2023 · 2 comments
Open

Sharing a vanity domain with wildebeest #65

xortive opened this issue Jan 10, 2023 · 2 comments

Comments

@xortive
Copy link

xortive commented Jan 10, 2023

I have the domain alon.so -- I'd like to use it with wildebeest such that my mastodon username is matt@alon.so but I don't want the wildebeest read-only UI on alon.so -- I'm OK with hosting any api routes off of alon.so however.

@kylekorth
Copy link

My assumption is this would need to be something like Mastadon uses with LOCAL_DOMAIN and WEB_DOMAIN variablesspecified but you would still need to manage the well-known deployment on the local domain.

  • LOCAL_DOMAIN=alon.so
  • WEB_DOMAIN=social.alon.so
  • a user managed route for alon.so/.well-known/host-meta?resource=acct:@alon.so which just queries social.alon.so/.well-known/host-meta?resource=acct:matt@.so with the metadata so searches can work.

@IDisposable
Copy link

@xortive You can hang just the CloudFinger .webfinger handler worker on your main domain to handle the identity lookups and host the WildeBeest on a subdomain if desired.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants