detroit-grancher - publish website via dedicated git branch
The Grancher tool utilizes the Grancher library to publish a
project's website via a dedicated git branch. Typically this
Note that his plug-in has been generally superseded by the
The following options can be used in Detroit assembly files for defining a github service.
remote - The remote to use (defaults to 'origin').
branch - The branch into which to save the files.
keep - List of any files/directory to not overwrite in branch.
keep_all - Do not remove any files currently in the branch.
sitemap - List of directories and files to transfer.
If a single directory entry is given then the contents
of that directory will be transferred. Defaults to
If you keep your website in a project sub-directory called either
www, and failing those,
then the defaults settings are likely sufficient.
grancher: active: true
If the files to copy to the gh-pages branch are more entailed, use
a mapping of source to destination. For example, if we want to copy
all the files in
site/ to gh-pages, but also all the files in
to a directory called
doc we could use:
grancher: sitemap: site: . doc: doc
However, this isn't usually necessary, since a soft link could be used instead.
$ ln -s doc site/doc
You can check soft-links into with git and they will be transferred as
if the real file when copied to the gh-pages file. So a more complex
sitemap is really only needed when more specific selections or
complex globs are needed.
For more information:
Copyright (c) 2010 Thomas Sawyer, Rubyworks
Detroit Grancher is distributable in accordance with the GPLv3 license.
detroit(1), git(1), detroit-github(5)