commit | 0d6896b259767659c14920b9d280ce152a135795 | [log] [tgz] |
---|---|---|
author | kathyssaunders <oskssaunders@gmail.com> | Wed May 04 10:57:48 2016 -0700 |
committer | kathyssaunders <oskssaunders@gmail.com> | Wed May 04 10:57:48 2016 -0700 |
tree | 294e644daec43011b91482fd1285d4f47e5ca7a1 | |
parent | 06971cbfe262a597ca76ec45520a916dbb26fbd4 [diff] |
Added Wiki to menu
http://quarks.incubator.apache.org/
This procedure was borrowed in part from the apex site. (https://git-wip-us.apache.org/repos/asf?p=incubator-apex-site.git) except we use jekyll.
The master branch of this repo contains the source files that are used to generate the HTML that ultimately gets pushed to the incubator site. The asf-site
branch is where the actual generated files are stored. Note that this branch must contain exactly one folder called content
, and so has been checked out as an orphan branch with its own commit history apart from the master branch. See the Contributing section below.
Through a gitpubsub mechanism on the apache.org server, files are taken from the asf-site
branch and pushed to the live server.
If you would like to make a change to the site:
master
If you are a committer, do the following:
Update the master branch with your (or a Pull Request's) change.
Push updated master to the asf remote master (https://git-wip-us.apache.org/repos/asf/incubator-quarks-site.git)
Run build.sh
from the master branch directory (requires jekyll). This checks out and updates the asf-site
branch with a new commit of the build from the current branch
At this point, you should be on the asf-site
branch. Simply push this branch to the asf remote with git push origin asf-site
and the site will automatically be updated within seconds.
Note: If you want to try out the website locally on the asf-site branch before you push, you can do so with jekyll serve -d content --skip-initial-build
and point your browser to http://localhost:4000