How to setup domain for Takahe

Howtos
1

Is there something that we can do after we filled up the form?

2

For Takahe, you will need to consider the following parts.

  • The “Service Domain”. This is the domain of your “instance” which your clients will be using to interact with your account.
  • The “frontend domain” is optional, it will be the domain where your frontend application (currently, elk) is available.
  • Your “identity domain” will be the domain part of the user handle.

With these in mind, you will need to configure the following:

  • DNS records for your “service domain”, which needs to be pointed to our gateway server (gateway.communick.host)
  • A way for your web server at your identity domain to respond to webfinger queries. (if the identity domain is different from the service domain)

To give my own account as example, I have an @raphael@lullis.net user being handled by takahe, which means that lullis.net is my identity domain. and I’ve set up activitypub.lullis.net to be the service domain.

I have placed a file on the “https://lullis.net/.well-known/webfinger” URL that returns the following:

{
  "subject": "acct:raphael@lullis.net",
  "aliases": [
    "https://activitypub.lullis.net/@raphael/"
  ],
  "links": [
    {
      "rel": "http://webfinger.net/rel/profile-page",
      "type": "text/html",
      "href": "https://activitypub.lullis.net/@raphael/"
    },
    {
      "rel": "self",
      "type": "application/activity+json",
      "href": "https://activitypub.lullis.net/@raphael@lullis.net/"
    }
  ]
}

Take a look at the contents of the file above and replace with your own values on “subject”, “aliases” and “href”.