Kite is a set of libraries, tools, examples, and documentation focused on making it easier to build applications on top of the Hadoop ecosystem.
This repository contains the Kite SDK Guide.
If you haven't already done so, install Jekyll on your system. You may also need to install Coderay for syntax highlighting:
sudo gem install coderay
Then, you can build the current version of the documentation by executing:
jekyll build
This will compile the documentation into HTML in a directory called _site.
Some pages depend on documentation generated by maven. To include the content for these pages, generate the maven site from the root of a kite working copy. The command to run the maven site plugin is:
export MAVEN_OPTS="$MAVEN_OPTS -Xmx1g"
mvn post-site site:stage -DstagingDirectory=/tmp/kite-stage -DtopSiteURL=http://kite-sdk.org
Next, link the created docs into the HTML includes folder:
ln -s /tmp/kite-stage/docs/<version> _includes/current
Pages will be built using content from the staged site when the site is generated.
You can view a live version of the documentation by executing:
jekyll serve --baseurl ''
and then viewing the site at localhost:4000.
- Ensure the the version section of
_config.yml
is correct for the current Kite version. - Ensure the
_includes/current
link points to the maven site built for the current Kite version. - Update the
baseurl
for the site you will deploy. For example,/docs/staging
or/docs/<version>
- Build the documentation site:
jekyll build
- Check out the
gh-pages
branch of the kite repository - Delete the
docs/staging/
directory if it exists.
cd docs
rm -rf staging/
- Copy the
_site
directory todocs/staging/
cp -r ../../kite-docs/_site/ staging
- Commit and push the staging site.
git add .
git commit -m "<RELEASE ISSUE>: Deploying staging site"
- Stage the current master and ensure it is correct
- Update
_config.yml
to the correctbaseurl
for the current Kite version,/docs/<version>
. - Builde the documentation site with
jekyll build
- Delete the
docs/staging/
directory if it exists.
cd docs
rm -rf <version>/
- Copy the
_site
directory todocs/<version>/
cp -r ../../kite-docs/_site/ <version>
- Commit and push the site.
git add .
git commit -m "<RELEASE ISSUE>: Deploying staging site"
#!/bin/bash
REMOTE=origin
GH_PAGES=/path/to/kite-gh-pages
KITE_DOCS=/path/to/kite-docs
VERSION=staging
RELEASE_ISSUE=<release-issue-id>
# remove the target if it exists
cd $GH_PAGES/docs
rm -rf $VERSION
# copy the site content
cp -r $KITE_DOCS/_site $VERSION
cd $VERSION
# prepare a commit with the changes
git add .
git commit -m "$RELEASE_ISSUE: Deploying $VERSION site"
git push $REMOTE master