Hi Andy The code's all in the repository! :)
We hook into the travis build system to do this, with some simple scripts. On the post-merge-to-main branch travis run, if the tests pass, then it pushes the built site files to a separate github repository which is hosted as a github pages site. This uses the travis secret key functionality, meaning that anyone can merge-request to the jobs site, but control of the templates, build logic, etc, is held in a more restricted repo. I was meaning to write up our repo/code structure at some point, so may do this when I'm back from holidays. Steve On Sun, Oct 4, 2015 at 10:39 PM Andy Robinson <a...@reportlab.com> wrote: > Salim, Hyde looks very impressive. > > I've been helping a few small communities build sites with Jekyll and > GitHub Pages, where the page generation is done by GitHub after you > commit. Do you mind me asking what does this for Hyde? Is some agent > running somewhere else which updates all the pages and commits the lot > after each job is committed? > > - Andy > _______________________________________________ > python-uk mailing list > python-uk@python.org > https://mail.python.org/mailman/listinfo/python-uk >
_______________________________________________ python-uk mailing list python-uk@python.org https://mail.python.org/mailman/listinfo/python-uk
