Comments on: Migrating project websites to github pages with sake tasks, new websites with jekyll_generator

By: Thomas

Thomas — Sat, 27 Jun 2009 13:28:32 +0000

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

kylemac — Wed, 25 Feb 2009 19:25:21 +0000

Thanks for the help, again awesome project and great tutorial – super helpful. (wow i use too many adjectives)

By: Dr Nic

Dr Nic — Wed, 25 Feb 2009 05:15:23 +0000

@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

kylemac — Wed, 25 Feb 2009 04:25:02 +0000

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

Peter Jaros — Tue, 27 Jan 2009 03:43:53 +0000

@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

Dr Nic — Mon, 12 Jan 2009 03:42:06 +0000

@transfire – the raw sake task is http://github.com/drnic/sake-tasks/raw/master/github/pages/migrate_website.sake

By: trans

trans — Mon, 12 Jan 2009 03:35:40 +0000

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

Sudhindra Rao — Sun, 11 Jan 2009 20:54:52 +0000

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

By: Dr Nic

Dr Nic — Tue, 23 Dec 2008 00:36:55 +0000

@pjmm – thank, updated.

By: pjmm

pjmm — Tue, 23 Dec 2008 00:21:41 +0000

Thanks: looks great… Small correction for us newbies: I think the line

sudo gem source http://gems.github.com

should read

sudo gem source -a http://gems.github.com

in order to actually push the given source onto the list of sources.