Comments on: Migrating project websites to github pages with sake tasks, new websites with jekyll_generator http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/ Ruby makes Rails, Javascript makes Ajax, Dr Nic makes Magic Mon, 30 Apr 2012 17:04:45 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: lose belly fat http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/comment-page-1/#comment-212551 lose belly fat Tue, 08 Jun 2010 11:57:23 +0000 http://drnicwilliams.com/?p=380#comment-212551 I just happened to stumble on this blog while surfing. This is a very insightful article. I really appreciated the info. I just happened to stumble on this blog while surfing. This is a very insightful article. I really appreciated the info.

]]> By: ユナイテッド航空 マイレージ http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/comment-page-1/#comment-208035 ユナイテッド航空 マイレージ Wed, 05 May 2010 07:16:23 +0000 http://drnicwilliams.com/?p=380#comment-208035 Thanks! Recently I've been reading the RSpec beta book from Pragmatic Programmers, and it was not too much clear for me. Now I th Thanks! Recently I’ve been reading the RSpec beta book from Pragmatic Programmers, and it was not too much clear for me. Now I th

]]> By: Thomas http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/comment-page-1/#comment-181422 Thomas Sat, 27 Jun 2009 13:28:32 +0000 http://drnicwilliams.com/?p=380#comment-181422 The <code>git submodule update --init</code> is IIUC equivalent to <code> git submodule init # register any new submodules in .gitmodules into .git/config git submodule update # update the local dir </code> Very useful post, thanks very much. -- Thomas The git submodule update --init is IIUC equivalent to


git submodule init # register any new submodules in .gitmodules into .git/config
git submodule update # update the local dir

Very useful post, thanks very much.

– Thomas

]]> By: kylemac http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/comment-page-1/#comment-158783 kylemac Wed, 25 Feb 2009 19:25:21 +0000 http://drnicwilliams.com/?p=380#comment-158783 Thanks for the help, again awesome project and great tutorial - super helpful. (wow i use too many adjectives) Thanks for the help, again awesome project and great tutorial – super helpful. (wow i use too many adjectives)

]]> By: Dr Nic http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/comment-page-1/#comment-158714 Dr Nic Wed, 25 Feb 2009 05:15:23 +0000 http://drnicwilliams.com/?p=380#comment-158714 @kyle - yeah I discovered that issue for user home pages recently. The generator was built for project pages (e.g. drnic.github.com/some_project) rather than drnic.github.com user pages. So the generator code needs fixing to support this. For the [rejected] issue - you find that you'll forever have either master or gh-pages rejected, depending if you're in root or the website folder. Its not an issue. To find out what is broken with a faulty rake command, pass --trace to get a stack trace. It will probably be issues relating to the first paragraph. Check the generated code that urls etc are correct. Ping again if you can't figure it out. @kyle – yeah I discovered that issue for user home pages recently. The generator was built for project pages (e.g. drnic.github.com/some_project) rather than drnic.github.com user pages. So the generator code needs fixing to support this.

For the [rejected] issue – you find that you’ll forever have either master or gh-pages rejected, depending if you’re in root or the website folder. Its not an issue.

To find out what is broken with a faulty rake command, pass –trace to get a stack trace. It will probably be issues relating to the first paragraph. Check the generated code that urls etc are correct. Ping again if you can’t figure it out.

]]> By: kylemac http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/comment-page-1/#comment-158706 kylemac Wed, 25 Feb 2009 04:25:02 +0000 http://drnicwilliams.com/?p=380#comment-158706 This has been amazingly helpful, not only play with Jekyll but get a better understanding of github in general (as I am a noob). I ran into an issue with the sake migrations, likely due to something I did. My errors read: ! [rejected] gh-pages -> gh-pages (non-fast forward) error: failed to push some refs to 'git@github.com:kylemac/kylemac.github.com.git' and rake aborted! can't convert true into String ----any ideas here? any help would be amazing. This has been amazingly helpful, not only play with Jekyll but get a better understanding of github in general (as I am a noob).

I ran into an issue with the sake migrations, likely due to something I did. My errors read:

! [rejected] gh-pages -> gh-pages (non-fast forward)
error: failed to push some refs to ‘git@github.com:kylemac/kylemac.github.com.git’

and

rake aborted!
can’t convert true into String

—-any ideas here? any help would be amazing.

]]> By: Peter Jaros http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/comment-page-1/#comment-152821 Peter Jaros Tue, 27 Jan 2009 03:43:53 +0000 http://drnicwilliams.com/?p=380#comment-152821 @trans: Actually, that's a pretty common thing to do. It might be better done as a non-branch ref, but being a branch isn't that terrible. Remember, this is git: you don't have to have the gh_pages branch in *your* repo for it to be in GitHub's. :) @trans: Actually, that’s a pretty common thing to do. It might be better done as a non-branch ref, but being a branch isn’t that terrible. Remember, this is git: you don’t have to have the gh_pages branch in *your* repo for it to be in GitHub’s. :)

]]> By: Dr Nic http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/comment-page-1/#comment-150209 Dr Nic Mon, 12 Jan 2009 03:42:06 +0000 http://drnicwilliams.com/?p=380#comment-150209 @transfire - the raw sake task is http://github.com/drnic/sake-tasks/raw/master/github/pages/migrate_website.sake @transfire – the raw sake task is http://github.com/drnic/sake-tasks/raw/master/github/pages/migrate_website.sake

]]> By: trans http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/comment-page-1/#comment-150208 trans Mon, 12 Jan 2009 03:35:40 +0000 http://drnicwilliams.com/?p=380#comment-150208 I was pleasantly surprised by the new Pages feature, but I was terribly disappointed to see it use a branch. I simply won't let GitHub pollute my branches this way. Not only does it decouple the version of the website from that of the rest of the project, but it misrepresents the intent of a branch. For instance, consider if someone created an automated tool that reported on the differences between all the branches and the current master, the gh_pages branch would require special exception, in this case just to satisfy GitHub. So I'm glad to see a work around, unfortunately it look like it only mitigates the issue, rather than actually solves it. I will probably not bother and just host my site on rubyforge.org instead. But I would like to as least see the code for this. Do you think you could post the sake task as a Gist? Thanks. I was pleasantly surprised by the new Pages feature, but I was terribly disappointed to see it use a branch. I simply won’t let GitHub pollute my branches this way. Not only does it decouple the version of the website from that of the rest of the project, but it misrepresents the intent of a branch. For instance, consider if someone created an automated tool that reported on the differences between all the branches and the current master, the gh_pages branch would require special exception, in this case just to satisfy GitHub. So I’m glad to see a work around, unfortunately it look like it only mitigates the issue, rather than actually solves it. I will probably not bother and just host my site on rubyforge.org instead. But I would like to as least see the code for this. Do you think you could post the sake task as a Gist? Thanks.

]]> By: Sudhindra Rao http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/comment-page-1/#comment-150159 Sudhindra Rao Sun, 11 Jan 2009 20:54:52 +0000 http://drnicwilliams.com/?p=380#comment-150159 Dr. Nic, I liked what you did with Jekyll. This is just wonderful. Happy New Year to you.. I mean to all of us. Sudhindra Dr. Nic,
I liked what you did with Jekyll. This is just wonderful.
Happy New Year to you.. I mean to all of us.
Sudhindra

]]>