On 13/05/2020 15:50, Bill Blough wrote:
On Wed, May 13, 2020 at 08:29:47AM +0100, Roger Leigh wrote:
To follow up,
I have been able to commit and push to xalan-site (git). However, I'm not
sure that directly affected the production website. I assume there's some
job which updates the site from version control, but I don't know if that's
been updated to work with the new git repo. Does anyone know how this
works, and who is responsible for it?
As I understand it, it's all controlled by the .asf.yaml configuration [1].
So pushing a .asf.yaml file with the appropriate config to the
appropriate branch should make it happen automatically from that point
forward.
Though, looking at the docs, it doesn't seem possible to specify an arbitrary
directory to deploy from, so we might have to move the contents of docs/xalan
to /content or /output to make it work correctly.
A .asf.yaml with
publish:
whoami: master
committed to the root of master and docs/xalan moved to /content should do
the trick, I think.
[1]https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories
Thanks Bill, that's now working.
I couldn't get it to work from a /content directory, even with pelican
enabled which is what the linked docs say it's for. As a result I moved
all the content to the root, and the website is still being served OK.
If I could find out how to do that then I could look at moving the
content from gh-pages directly to the xalan-site repository. Though it
might well require the root page to be converted to markdown, too. I
didn't want to mess with that for now. However, if there are no
objections to dropping stylebook in favour of simple markdown, I'll be
happy to convert that--it's only a single page plus some links. It
might not look as nice though; I'm no designer.
Kind regards,
Roger
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
