On Tue, Jan 26, 2016 at 2:49 PM, Lou Burnard
On 26/01/16 15:54, Hugh Cayless wrote:
I've done it, but it's not hard:
Thanks!
1) Make the html-web target in the branch you want 2) git checkout gh-pages 3) cd to the root of the repo
er, which repo exactly?
4) rsync -av P5/Guidelines-web/en/html/ ./ (i.e. copy the HTML files to the root directory)
root of what?
The TEI repo
5) git add, commit, push (if your changes mean new files, you'll need to
explicitly add them)
new HTML files you mean?
Yeah, if you've defined a new element, for example, you'll have a new reference page for it.
"gh-pages" is just a branch that has HTML content in it. When you push it,
GitHub publishes it to the github.io site.
We could automate this, but it seems it might be a good thing to have a site that's a bit more stable than Jenkins, which updates with every push, and that allows us to put up builds from branches without doing anything special. What do you all think?
I'm not sure what you're suggesting but I'm not very keen on cluttering up the repo with lots of versions of generated HTML.
They only exist in the branch, so they're not really cluttering anything
up.
On Tue, Jan 26, 2016 at 7:35 AM, Lou Burnard < lou.burnard@retired.ox.ac.uk> wrote:
I've now made some further revision to the structure of the chapter. Does
the github.io version update itself automatically, or do I need to do something ?
On 26/01/16 11:25, Lou Burnard wrote:
Thanks for the quick reaction James. Some comments below
--
tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived