Shingo Furuyama ee7fdfc45d [MINOR] Modify the description of POST /sessions/{sessionId}/completion 4 lat temu
..
_data 393c16201a [MINOR][BUILD] Update docs version for 0.8.0-incubating-SNAPSHOT 4 lat temu
_includes be3fe03457 [LIVY-384][DOCS] Added ability to build Livy Docs 7 lat temu
_layouts be3fe03457 [LIVY-384][DOCS] Added ability to build Livy Docs 7 lat temu
_plugins fc22da9194 [LIVY-141][LIVY-175][DOCS] Update javadocs and scaladocs and include in Docs build 6 lat temu
assets be3fe03457 [LIVY-384][DOCS] Added ability to build Livy Docs 7 lat temu
Gemfile be3fe03457 [LIVY-384][DOCS] Added ability to build Livy Docs 7 lat temu
Gemfile.lock f99cc32df3 [MINOR] Update version of ffi. 6 lat temu
README.md fc22da9194 [LIVY-141][LIVY-175][DOCS] Update javadocs and scaladocs and include in Docs build 6 lat temu
_config.yml be3fe03457 [LIVY-384][DOCS] Added ability to build Livy Docs 7 lat temu
index.md be3fe03457 [LIVY-384][DOCS] Added ability to build Livy Docs 7 lat temu
programmatic-api.md 50e4efe446 [BUILD] Bump master version to 0.7.0. 5 lat temu
rest-api.md ee7fdfc45d [MINOR] Modify the description of POST /sessions/{sessionId}/completion 4 lat temu

README.md

Apache Livy Documentation

This documentation is generated using Jekyll.

How to deploy the documentation

Installing Jekyll and dependencies

The steps below will install the latest Jekyll version and any dependencies required to get this documentation built.

1. sudo gem install jekyll bundler
2. cd docs
3. sudo bundle install

For more information, see Installing Jekyll.

Running locally

Before opening a pull request, you can preview your contributions by running from within the directory:

1. cd docs
2. bundle exec jekyll serve --watch
3. Open http://localhost:4000

API Docs (Scaladocs and Javadocs)

You can build just the Livy javadocs by running mvn javadoc:aggregate from the LIVY_HOME directory, or the Livy scaladocs by running mvn scala:doc in certain modules. (Scaladocs do not currently build in every module)

When you run jekyll build in the docs directory, it will also copy over the scaladocs and javadocs for the public APIs into the docs directory (and then also into the _site directory). We use a jekyll plugin to run the api builds before building the site so if you haven't run it (recently) it may take some time as it generates all of the scaladoc and javadoc using Maven.

NOTE: To skip the step of building and copying over the Scala and Java API docs, run SKIP_API=1 jekyll build.

Publishing Docs to [livy.incubator.apache.org]

  1. Build Livy Docs (cd docs then bundle exec jekyll build).
  2. Copy the contents of docs/target/ excluding assets/ into a new directory (eg. 0.4.0/) and move it into the docs/ directory in your local fork of apache/incubator-livy-website.
  3. If nesesary, update the latest symlink to point to the new directory.
  4. Open a pull request to apache/incubator-livy-website with the update.

Note: If you made any changes to files in the assets/ directory you will need to replicate those changes in the corresponding files in apache/incubator-livy-website in the pull request.