.well-known/atproto-did returns 404

[justinmk]

Problem:

Since migrating to hugo, https://neovim.io/.well-known/atproto-did returns 404 not found, even though:

• it exists at ./static/.well-known/atproto-did
• hugo build copies it to ./public/

Analysis

• Searched actions/deploy-pages issue tracker, no matches for "dot", "exclude", "ignore", etc.
• Likely root cause: Overly restrictive tar-file requirements (leading ./ needed) actions/deploy-pages#203

Potential fixes

1. use a path that does not start with a dot
   • this would be preferrable, @echasnovski is this possible ?
2. switch to peaceiris/actions-gh-pages
3. do a manual tar step like below (AI generated, idk):

- name: Create and upload artifact with fixed tar paths
  run: |
    cd public
    tar --create --verbose --file=../pages-artifact.tar \
      --transform='s|^|./|' * .*/  # Key: --transform adds ./ prefix; * for files, .*/ for dotdirs
    cd ..
  shell: bash

- name: Upload fixed artifact
  uses: actions/upload-pages-artifact@v3
  with:
    path: pages-artifact.tar  # Upload the custom tar directly

[echasnovski]

use a path that does not start with a dot

* this would be preferrable, [@echasnovski](https://github.com/echasnovski) is this possible ?

I am afraid, it is not. The /.well-known/ is a convention for web services to expose specific information. In this particular case - verify that neovim.io URL is associated with did:plc:635xovhsdw27inbgxukm3qtp Decentralized identifier used for ATProto services (like Bluesky). Currently it shows "Invalid handle" because it can not verify this. This also means that link https://bsky.app/profile/neovim.io stopped working.

If resolving this is for some reason not possible, there is a way to do the same with DNS record. Here is the guide. Relevant step is to create the DNS record of TXT type for the neovim.io address:

• Set the domain: _atproto
• Set the type: TXT
• Set the value field (also sometimes called “data”): did=did:plc:635xovhsdw27inbgxukm3qtp

This should create a domain record at _atproto.. After this is done, please ping me so that I can trigger verification.

Exposing /.well-known/atproto-did looks more preferable to me since it improves the bus factor, but DNS record also works.

[justinmk]

This was a bunny trail....

After switching the GHA publisher action #401 , https://github.com/neovim/neovim.github.io/tree/gh-pages shows that the file is in the gh-pages branch. But it is not clear to me which Pages settings are wanted:

If it doesn't start working afte some cache timeout, I am out of ideas. I guess TXT record is the only other option.

Although, I am not convinced the gh-pages branch is actually getting deployed. Maybe there is some other configuration needed.

[justinmk]

Trying these settings now, which triggered a Pages Deploy from gh-pages branch. Will wait a bit for cache to expire.

[echasnovski]

You are probably aware, but https://neovim.io/.well-known/atproto-did still returns 404 (just from Neovim's template now). I am trying to look into it, but it is hard to debug without knowing which GitHub Pages config is currently in use. The file is indeed served locally, but not on GitHub Pages.

The solution here seems to be to put a .nojekyll file in the root of the served site. The gh-pages branch does contain it at the moment, but I also notice that it is not up to date with main branch. Commits are five hours older and it says "serving 12837fc".

This makes me think that deployment is not done from gh-pages now, which I think is the most straightforward way to handle this. Otherwise, there needs to be a step in deployment ensuring that there is a '.nojekyll' file, which I don't know how to debug.

[echasnovski]

Aha, I see now. Could you try applying the following patch:

diff --git a/.github/actions/build-site/action.yaml b/.github/actions/build-site/action.yaml
index 4b2586c..563a55c 100644
--- a/.github/actions/build-site/action.yaml
+++ b/.github/actions/build-site/action.yaml
@@ -20,4 +20,7 @@ runs:
         HUGO_ENV: production
       run: |
         hugo --gc --minify --baseURL "$BASE_URL"
-
+    - name: Add nojekyll
+      shell: bash
+      run: |
+        touch public/.nojekyll

It also looks like 'build.yml' workflow is not needed.

[justinmk]

@echasnovski I created the TXT record. Looks like https://bsky.app/profile/neovim.io is working now.

The solution here seems to be to put a .nojekyll file ...
This makes me think that deployment is not done from gh-pages now,

It was, or was attempted, and I tried all different kinds of settings, but it didn't work.

It also looks like 'build.yml' workflow is not needed.

That's just a sanity check for pull requests.

[echasnovski]

It was, or was attempted, and I tried all different kinds of settings, but it didn't work.

I am pretty sure that this patch would have fixed it.

@echasnovski I created the TXT record. Looks like https://bsky.app/profile/neovim.io is working now.

Verified the domain and there is no "Invalid handle" now. Thank you for taking a look 🙏