From de59fdb1fc89ceb7f4828ff8cdf36a1b03636f7f Mon Sep 17 00:00:00 2001 From: Samuel Ryan Date: Fri, 24 Jan 2025 19:07:50 +0800 Subject: [PATCH] docs: Example using GitHub Pages to verify a domain --- .nojekyll | 0 .well-known/atproto-did | 1 + CNAME | 1 + README.md | 15 +++++++++++++++ 4 files changed, 17 insertions(+) create mode 100644 .nojekyll create mode 100644 .well-known/atproto-did create mode 100644 CNAME create mode 100644 README.md diff --git a/.nojekyll b/.nojekyll new file mode 100644 index 0000000..e69de29 diff --git a/.well-known/atproto-did b/.well-known/atproto-did new file mode 100644 index 0000000..be844a6 --- /dev/null +++ b/.well-known/atproto-did @@ -0,0 +1 @@ +did:plc:ilsghiel5jfpukzc5wzu5rmr diff --git a/CNAME b/CNAME new file mode 100644 index 0000000..b8cb947 --- /dev/null +++ b/CNAME @@ -0,0 +1 @@ +gh.handles.net diff --git a/README.md b/README.md new file mode 100644 index 0000000..ee46d9c --- /dev/null +++ b/README.md @@ -0,0 +1,15 @@ +# Verify domain on Bluesky using GitHub Pages + +Scenario: you have an apex domain but no web server and for some reason you are +unable to use the DNS verification method (e.g: TXT records aren't support, +underscores aren't supported, Bluesky doesn't seem to be able to verify your +records). The instructions that follow enable domain verification using GitHub +Pages in this rare situation. + +1. Create a new GitHub repository from this template +2. Modify the contents of `.well-known/atproto-did` to contain your `did` +3. Via your repository settings go to Pages then select the "main" branch to deploy from +4. Add your domain (e.g: example.com) +5. Via your DNS records manager, [point your domain to GitHub Pages](https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site) either an `A` record to `185.199.108.153` or a `ALIAS/CNAME` with `username.github.io` + +After a few minutes, your domain will become active and it can be added to Bluesky.