regarding post categories

Question

regarding post categories

dotkay opened this issue 7 years ago · comments

I can get the post categories working when I build it locally, but they don't show up in github pages :-( can you please help? Thanks,

Chayoung You · Answer 1 · Fri Aug 11 2017 15:56:06 GMT+0800 (China Standard Time)

Hi, actually this theme uses jekyll-archives gem, which is not supported by GitHub Pages. This is the reason of using Travis CI to build the website.

The only thing you need to change in .travis.yml is env.global.secure value. Go to 'Settings > Personal access tokens' in GitHub, and generate a new token. Then using travis gem, encrypt that token in your blog repository.

gem install travis
travis encrypt TOKEN="yourtoken"

Then it'll output something like secure: "...", then update the .travis.yml with the value.

kalyan · Answer 2 · Fri Aug 11 2017 16:26:33 GMT+0800 (China Standard Time)

Thanks again.
I tried travis encrypt TOKEN="..." but it throws the following:

repository not known to https://api.travis-ci.org/: dotkay/dotkay.github.io

I tried playing around with caps (DOTKAY), etc. (after some Googling around), but didn't help

Chayoung You · Answer 3 · Fri Aug 11 2017 16:30:30 GMT+0800 (China Standard Time)

Hi, you have to enable Travis CI for that repository, too. Go to https://travis-ci.org, login and navigate to 'Acconts'. Then you'll see the list of your repository. Turn on the switch for dotkay/dotkay.github.io, and have a check again.

kalyan · Answer 4 · Fri Aug 11 2017 16:53:18 GMT+0800 (China Standard Time)

Ah, thanks. Just did that... Let me build and check...

Chayoung You · Answer 5 · Fri Aug 11 2017 17:11:25 GMT+0800 (China Standard Time)

Ah you're using *.github.io, then the master branch will be used as the source directory of GitHub Pages. But we build the site ourselves, so the result of jekyll build should goes to the master branch. Try change the name of current master branch to other, and make master branch by git checkout --orphan master with an initial commit.

Also you should modify .travis.yml, because of the branch names. Replace master to your source branch, and gh-pages to master.

kalyan · Answer 6 · Sun Aug 13 2017 01:02:23 GMT+0800 (China Standard Time)

thanks. trying it now - trying to resolve the travis build errors. should the master and branch have the same set of files?

Chayoung You · Answer 7 · Sun Aug 13 2017 01:09:11 GMT+0800 (China Standard Time)

You only make commits to source branch, then Travis CI pushes generated files to destination branch.

Chayoung You · Answer 8 · Sun Aug 13 2017 01:11:53 GMT+0800 (China Standard Time)

It seems that you switched two branches, you make Travis CI to push to release branch, so the categories/misc directory was generated, but GitHub Pages still using master branch, so jekyll-archives gem is not enabled on the actual site.

kalyan · Answer 9 · Sun Aug 13 2017 01:14:48 GMT+0800 (China Standard Time)

so github pages should use the release branch eventually? am confused because travis builds my master properly, but errors out on release :-( but i did the mistake of committing to release branch as well.. have to somehow revert those

kalyan · Answer 10 · Sun Aug 13 2017 01:15:54 GMT+0800 (China Standard Time)

let me make the destination as master (in travis.yml) and source as release and see what happens

kalyan · Answer 11 · Sun Aug 13 2017 12:47:32 GMT+0800 (China Standard Time)

i finally got around using only master and now the travis builds are going through fine, and it's also generating the categories/misc and i also see the <a tag in the index.html. but it still doesn't show up when published. can you please help me figure out where I am wrong? only when you have time. I think I am close to the solution, but don't know the last mile

Chayoung You · Answer 12 · Sun Aug 13 2017 16:17:37 GMT+0800 (China Standard Time)

To be clear:

First, you need two separate branches: master for actual HTML files, and source branch, let's say it source.
The content of your current master branch should goes to source. You can just rename the branch and push by git branch -m source, git push origin source.
Travis CI will push to master, but you need to create it. Try git checkout --orphan master, git commit --allow-empty -m "Initial commit", git push -f origin master.

Try starting from this .travis.yml:

language: ruby
sudo: false
cache: bundler
rvm:
  - 2.3.3
env:
  global:
    - secure: "..."
before_install:
  - gem update --system
  - gem update --remote bundler
before_script:
  - git config --global user.name "$(git --no-pager show --no-patch --format='%an')"
  - git config --global user.email "$(git --no-pager show --no-patch --format='%ae')"
script:
  - git clone -b master --depth 1 "https://${TOKEN}@github.com/${TRAVIS_REPO_SLUG}.git" _site >/dev/null 2>&1
  - rm -rf _site/*
  - bundle exec jekyll build
after_success:
  - cd _site
  - git add -A
  - git commit -m "Updated to $(git rev-parse --short $TRAVIS_COMMIT) at $(date -u +'%Y-%m-%d %H:%M:%S %Z')"
  - git push "https://${TOKEN}@github.com/${TRAVIS_REPO_SLUG}.git" master >/dev/null 2>&1
branches:
  only:
    - source

kalyan · Answer 13 · Sun Aug 13 2017 23:07:35 GMT+0800 (China Standard Time)

thanks a lot. somehow, i thought i can get through my just having one master branch. let me try this now.

kalyan · Answer 14 · Mon Aug 14 2017 07:16:46 GMT+0800 (China Standard Time)

now travis builds fine, it creates categories/misc, etc. but I don't see it getting pushed to the master :-(
(meaning: i dont see _site and sub-directories in the master branch). But the travis build log (attached)

seems to indicate that it created it. How do I debug further?

Chayoung You · Answer 15 · Mon Aug 14 2017 11:11:50 GMT+0800 (China Standard Time)

I'm not sure, but can you try adding a space between - and secure in your .travis.yml?

kalyan · Answer 16 · Mon Aug 14 2017 11:17:51 GMT+0800 (China Standard Time)

wow! adding that one space worked! thank you so much! you're awesome!

Chayoung You · Answer 17 · Mon Aug 14 2017 12:49:08 GMT+0800 (China Standard Time)

Congrats! No problem :)

Zhao · Answer 18 · Thu Mar 01 2018 01:25:34 GMT+0800 (China Standard Time)

Thanks yous for the nice theme! Can I know how can I trigger the Travis build after I commit and push my code to master? I added the .travis.yml and committed it with the correct TOKEN, my repo was linked with Travis as well, however no build was triggered on Travis :(

Chayoung You · Answer 19 · Thu Mar 01 2018 01:42:44 GMT+0800 (China Standard Time)

Hi, @neo0907. The .travis.yml has following lines:

branches:
  only:
    - source

But your repository has master branch only. You should push your current master to source branch. The remote master branch is for the generated site content.

Rename your local master branch to source with git branch -m source
Make new master branch with git checkout --orphan master, git commit --allow-empty -m "Initial commit", git push -f origin master
Push your source branch with git checkout source, git push origin source

kalyan · Answer 20 · Thu Mar 01 2018 01:47:01 GMT+0800 (China Standard Time)

You can refer to mine. I push it to source.

…

On Wed, 28 Feb 2018 09:44 Chayoung You, ***@***.***> wrote: Hi, @neo0907 <https://github.com/neo0907>. The .travis.yml has following lines: branches: only: - source But your repository has master branch only. You should push your current master to source branch. The remote master branch is for the generated site content. - Rename your local master branch to source with git branch -m source - Make new master branch with git checkout --orphan master, git commit --allow-empty -m "Initial commit", git push -f origin master - Push your source branch with git checkout source, git push origin source — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AM5aDkM7totTIjwkJi9peNonK5CjBlw8ks5tZZAUgaJpZM4O0Vft> .

Zhao · Answer 21 · Thu Mar 01 2018 23:37:40 GMT+0800 (China Standard Time)

Thanks for the help! It now failed in Travis with error 128

$ git clone -b master --depth 1 "https://${TOKEN}@github.com/${TRAVIS_REPO_SLUG}.git" _site >/dev/null 2>&1
The command "git clone -b master --depth 1 "https://${TOKEN}@github.com/${TRAVIS_REPO_SLUG}.git" _site >/dev/null 2>&1" exited with 128.

I am suspecting something wrong with my secure value, I have generate the SECURE token with below code and added. However in my GitHub settings, it says this token has never been used. This doesn't look right, any ideas which part I missed? And in GitHub settings, I did give this token all the access on 'repo' scope.

travis encrypt TOKEN="yourtoken"

Chayoung You · Answer 22 · Fri Mar 02 2018 10:22:11 GMT+0800 (China Standard Time)

Oh, your source contains _site directory. This prevents git clone. Add proper .gitignore file to your source branch, and try cleaning with git clean -Xdf. Also I recommend you to clean your master branch, especially files or directories that start with ..

Zhao · Answer 23 · Sat Mar 03 2018 23:43:16 GMT+0800 (China Standard Time)

Thanks! It is now working properly 👍