On 3/3/2016 6:14 AM, Katherine Marsden wrote:
Most of my experience is with svn but I think that for Quarks it makes
sense to keep everything in git, so am guessing gitpubsub is the way
to go. I see this blog
https://blogs.apache.org/infra/entry/git_based_websites_available but
am having trouble finding more documentation. I guess we need an
asf-site branch for our repo and then commit the jekyll served website
to that, then file an INFRA issue to request gitpubsub?
I still need guidance on this but found this comment in a Jira issue
that explains how it works:
https://issues.apache.org/jira/browse/INFRA-10249?focusedCommentId=14729921&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14729921
It says:
"We create a repo for you (generally incubator-apex-site.git)
You create a branch called asf-site
You commit the raw html files to the asf site branch in 1 of two folder
layouts:
$REPO_ROOT/<raw html> **OR** $REPO_ROOT/content/<raw html>
If you opt for the 2nd layout, the *only* thing that can exist in the
root of the repo is the folder called content, otherwise your website
will not work properly.
Also, gitpubsub is not tied into any sort of build system, so you would
have to build the site somehow and then copy over the generated html
file to the repo in the above layout."
The apex repo is at
https://git-wip-us.apache.org/repos/asf?p=incubator-apex-site.git and
looking at the layout it looks like we would maintain the site on the
master branch and create an orphan branch asf-site which has just the
content directory which we create with jekyll serve -d content_tmp on
the master and then mv that to content the asf-branch. If there is a
way to just generate without serving we could have a build script like
apex's build.sh that would publish the site.
Does it sound like I am on the right track here? I appreciate an
assistance.
Kathey
