Skip to content

Commit

Permalink
docs: Example using GitHub Pages to verify a domain
Browse files Browse the repository at this point in the history
  • Loading branch information
shrink committed Jan 24, 2025
0 parents commit de59fdb
Show file tree
Hide file tree
Showing 4 changed files with 17 additions and 0 deletions.
Empty file added .nojekyll
Empty file.
1 change: 1 addition & 0 deletions .well-known/atproto-did
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
did:plc:ilsghiel5jfpukzc5wzu5rmr
1 change: 1 addition & 0 deletions CNAME
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
gh.handles.net
15 changes: 15 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -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.

0 comments on commit de59fdb

Please sign in to comment.