Self-hosting beyond the PDS and having a did:web
Hello, With little prior experience in self-hosting, I've managed to host a few ActivityPub instances, so I thought to myself - why not try hosting a whole ATproto stack, not just a PDS? I've got a domain for all of my sites, a subdomain (let's number it 1) for my PDS and a second subdomain where I was going to put an AppView running "anartia", a JavaScript-optional frontend. I've been following this guide so far: https://blog.lapyst.dev/posts/14-how-to-create-a-completely-independent-bluesky-atproto-account I've managed to get the PDS up and running, but it was not clear to me from this tutorial if did:web should overlap with my AppView subdomain. Then I've read that at:// should lead to my user identity, but then it must be something like username.subdomain2.domain.tld ... But then, according to the blog post, I need to serve a did.json and an atproto-did under ".well-known" on a subdomain that appears to be same as the did:web / alsoKnownAs. The blog post assumes the reader must know already how to make the directory ".well-known" (but where the domain should lead to? not the PDS per se, right?) and what to do with the instruction "Make sure that the DID document and all related data is accessible from web-clients, I.e. set the Access-Control-Allow-Origin header like so: add_header Access-Control-Allow-Origin "*";" - is this supposed to be merely a line added to the .json file? It doesn't feel like JSON, lol. Would be greatly appreciated if any of you could kindly clarify how should the subdomains be structured (note: it won't be a purely single-user instance; further down the road I want to self-host Ozone too) and what to do with ".well-known"! Thanks.