limepotato/akkoma
1
0
Fork 0
Code Pull requests Activity

Merge branch 'tusooa/caveats-webfinger' into 'develop'

Browse source 
Document some caveats of webfinger domain setting

See merge request pleroma/pleroma!3767
This commit is contained in:
feld 2022-11-03 22:24:38 +00:00
commit 9f708037d7
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/configuration/how_to_serve_another_domain_for_webfinger.md
View file

@ -42,8 +42,8 @@ config :pleroma, Pleroma.Web.Endpoint,
config :pleroma, Pleroma.Web.WebFinger, domain: "example.org"
```
- `domain` - is the domain for which your Pleroma instance has authority, it's the domain used in `acct:` URI. In our example, `domain` would be set to `example.org.
- `host` - is the domain used for any URL generated for your instance, including the author/actor URL's. In our case, that would be `pleroma.example.org.
- `domain` - is the domain for which your Pleroma instance has authority, it's the domain used in `acct:` URI. In our example, `domain` would be set to `example.org`. This is used in WebFinger account ids, which are the canonical account identifier in some other fediverse software like Mastodon. **If you change `domain`, the accounts on your server will be shown as different accounts in those software**.
- `host` - is the domain used for any URL generated for your instance, including the author/actor URL's. In our case, that would be `pleroma.example.org`. This is used in AP ids, which are the canonical account identifier in Pleroma and some other fediverse software. **You should not change this after you have set up the instance**.
### Configuring WebFinger domain