Google Git
Sign in
apache / calcite / refs/heads/master / . / site
tree: 225f18094734f8e2ee445a172caab54ac5c8ce82 [path history] [tgz]
  1. _data/
  2. _docs/
  3. _includes/
  4. _layouts/
  5. _plugins/
  6. _posts/
  7. _sass/
  8. community/
  9. css/
  10. develop/
  11. downloads/
  12. fonts/
  13. img/
  14. news/
  15. .asf.yaml
  16. .gitignore
  17. .htaccess
  18. _config.yml
  19. doap_calcite.rdf
  20. docker-compose.yml
  21. favicon.ico
  22. Gemfile
  23. index.html
  24. README.md
site/README.md

Apache Calcite docs site

This directory contains the sources/templates for generating the Apache Calcite website, calcite.apache.org. The actual generated content of the website is present in the calcite-site repository.

We want to deploy project changes (for example, new committers, PMC members or upcoming talks) immediately, but we want to deploy documentation of project features only when that feature appears in a release.

The procedure for deploying changes to the website is outlined below:

  1. Push the commit with the changes to the master branch of this repository.
  2. Cherry-pick the commit from the master branch to the site branch of this repository.
  3. Checkout the site branch and build the website either manually or using docker-compose (preferred).
  4. Commit the generated content to the master branch of the calcite-site repository following the Pushing to site instructions.

Manually

Setup your environment

Site generation currently works best with ruby-2.5.1.

  1. cd site
  2. git clone https://gitbox.apache.org/repos/asf/calcite-site.git target
  3. sudo apt-get install rubygems ruby2.5-dev zlib1g-dev (linux) Use RubyInstaller to install rubygems as recommended at https://www.ruby-lang.org/en/downloads/ (Windows)
  4. sudo gem install bundler gem install bundler (Windows)
  5. bundle install

Add javadoc

  1. cd ..
  2. ./gradlew javadocAggregate
  3. rm -rf site/target/javadocAggregate rmdir site\target\javadocAggregate /S /Q (Windows)
  4. mkdir site/target mkdir site\target (Windows)
  5. mv build/docs/javadocAggregate site/target for /d %a in (build\docs\javadocAggregate*) do move %a site\target (Windows)

Running locally

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

  1. bundle exec jekyll serve
  2. Open http://localhost:4000

Using docker

Setup your environment

  1. Install docker
  2. Install docker-compose

Build site

  1. cd site
  2. docker-compose run build-site

Generate javadoc

  1. cd site
  2. docker-compose run generate-javadoc

Running development mode locally

You can preview your work while working on the site.

  1. cd site
  2. docker-compose run --service-ports dev

The web server will be started on http://localhost:4000

As you make changes to the site, the site will automatically rebuild.

Pushing to site

  1. cd site/target
  2. git init
  3. git remote add origin git@github.com:apache/calcite-site.git
  4. git fetch
  5. git reset origin/master --soft

If you have not regenerated the javadoc and they are missing, restore them:

  1. git reset -- javadocAggregate/
  2. git checkout -- javadocAggregate/

Restore the avatica site

  1. git reset -- avatica/

  2. git checkout -- avatica/

  3. git add .

  4. Commit: git commit -m "Your commit message goes here"

  5. Push the site: git push origin master

Within a few minutes, gitpubsub should kick in and you'll be able to see the results at calcite.apache.org.

This process also publishes Avatica‘s web site. Avatica’s web site has separate source (under avatica/site) but configures Jekyll to generate files to site/target/avatica, which becomes an avatica sub-directory when deployed. See Avatica site README.