This Rakefile will abuse your master branch. It will go against the usual git flow, if that doesn't ride well with you, don't use this.
Too much wrangling with the dependencies on the Gemfile. My user page isn't some big project that everyone would use. I figured it's worth enough to sacrifice "best practices" for version control. It's just a user page, I don't want to pull my hair out trying to figure out dependencies in the build server when I add additional gems.
The Jekyll source of my site currently resides on another branch. master
only contains the /_site
contents.
- Make sure your source directory is on another branch other than
master
. - Add
/_site
to.gitignore
. Remove it in the git history if it's already added rake build
is the same asjekyll build
rake publish
fires off ajekyll build
and agit push origin master
on your/_site
folder.
- Goes into your
/_site
folder and initialize a git folder there. - Adds your git remote as it's git remote.
git add .
's that entire folder as part of a push intoorigin/master
This Rakefile is based off of the middleman-gh-pages
gem.
Why not use middleman? You're already using it on other projects and you've based this off entirely of that gh-pages gem.
The power of Jekyll Tumblr Import is too good to pass up :)