Github Pages compatibility

[stevenleeg]

Hey guys!

I'm noticing a bit of an issue when trying to verify your website with Github pages. I use GH pages to run my domain's website, however it appears that pages doesn't serve folders starting with a period (eg, .well-known), so I'm unable to verify my domain.

Anyone know of a workaround?

[MattSurabian]

You're right! It's cause of the . in the directory name, no worries:
https://help.github.com/articles/files-that-start-with-an-underscore-are-missing

[MattSurabian]

I'll add I opted for using the include directive in the _config.yml and it worked like a charm.

include: [".well-known"]

[stevenleeg]

This worked perfectly. Thanks!

On Wednesday, March 26, 2014 at 6:36 PM, Matthew Surabian wrote:

I'll add I opted for using the include directive in the _config.yml and it worked like a charm.
include: [".well-known"]

—
Reply to this email directly or view it on GitHub (#366 (comment)).

[wsargent]

where do you put the file on the filesystem? I'm still having no luck in generating it.

[MattSurabian]

@wsargent I put it in the root of my jekyll repo:

https://github.com/MattSurabian/mattsurabian.github.io

[wsargent]

That's where I have it, in both my gh-pages branch and my master branch. I see it in Github, but don't see a path to it: http://tersesystems.com/.well-known/keybase.txt is 404.

[malgorithms]

@wsargent did you try @MattSurabian 's solution with the config file?

We are strongly considering changing the default path of keybase proofs out of the ./well-known and just into the top folder now, due to this difficulty. Both because (a) it's apparently annoying in certain hosting platforms to host a dot folder, and (b) because some users aren't noticing the dot.

[wsargent]

I have tried include: [".well-known"] in the _config.yml file and I have
checked it and run "rake generate; rake deploy" and all that. Still no
dice. :-(

[malgorithms]

Ok, maybe someone else has an idea. Very frustrating!

[MattSurabian]

@wsargent is it possible to link to the github pages repo?

[wsargent]

@MattSurabian added you.

[MattSurabian]

@wsargent I believe the source of your trouble is this line:

source: source

I see you've already added a .well-known/keybase.txt in the source directory so it should be as simple as updating this line to this:

include: ["source/.well-known"]

I'd try it myself but didn't want to be too forward! Good luck!

[wsargent]

@MattSurabian I've added the line, but it doesn't seem to be working, even when I try "rake preview". This is bizarre.

[stevenleeg]

Have you tried just running 'jekyll serve --watch'?

On Thu, Mar 27, 2014 at 3:22 PM, Will Sargent notifications@github.com
wrote:

@MattSurabian I've added the line, but it doesn't seem to be working, even when I try "rake preview". This is bizarre.

Reply to this email directly or view it on GitHub:
#366 (comment)

[MattSurabian]

This seems like it might be an issue with Octopress, there are a old issues on the octopress github from people having trouble with dotfiles and octopress. Have you looked into the copydot rake task?

[MattSurabian]

Ah, looks like the rake file excludes dot named directories:
https://github.com/wsargent/tersesystems/blob/master/Rakefile#L230-L235

[DominikTo]

With Jekyll on GitHub Pages just add a file keybase.txt in your root and add the following header:

---
layout: none
permalink: .well-known/keybase.txt
---

[hallettj]

For those using Octopress who are having this issue, here is a fix.

Create an empty file in your source directory called ".nojekyll":

$ touch source/.nojekyll

Edit _config.yml and add this line:

include: [".well-known", ".nojekyll"]

Deploy as usual!

The Octopress rake tasks build your site locally and just upload the resulting static files into your master branch. Then Github builds your site a second time. (The second build usually has no effect since Jekyll does nothing to regular static files.) Since Octopress does not include _config.yml in your master branch, Github does not see your include setting and therefore excludes .well-known. But by including the .nojekyll file you instruct Github not to build the site itself, and to just serve the files as-is.

[tphummel]

adding include: [".well-known"] worked for me, as well as permalink: .well-known/keybase.txt. 👍

[huseyint]

@MattSurabian thanks bunch, worked like a charm!

[wakest]

thank you @hallettj this just solved a problem I was working on for hours!

[amanijoseph87]

Is there a way to add this on html

[Nircek]

Thanks. I think the issue should be closed due to being solved.

[OR13]

Adding a .nojekyll file to the directory that is served by github solved this for me.