Re: Auto-deploying the html version of the spec

Ok, the HTML version of the spec will now be automatically generated when
the master branch is updated.

>From now on you should make all your changes based on the master branch.
All pull requests will automatically default to the master branch.  There
isn't any reason for you to work on the gh-pages branch now, and it's
probably a mistake if you do.  You should NOT check in index.html to the
master branch either.

One minor benefit is that you can use the new compile.sh script (on unix
systems) to run bikeshed and compare the actual to the expected results.

We should probably clean up the gh-pages branch so that it contains only
just the files needed to display the spec, but there's no pressing need for
that right away.

On Fri, Jun 22, 2018 at 1:19 AM Matthew Paradis <matthew.paradis@bbc.co.uk>
wrote:

> I can do that Ray, will forward you details shortly.
>
>
>
> --
>
> Matthew Paradis
>
> Senior R&D Engineer – Audio,
>
> BBC Research & Development
>
>
>
> 030304 09889 | 07841 506241
>
> www.bbc.co.uk/rd/sound
>
>
>
> *From: *Raymond Toy <rtoy@google.com>
> *Date: *Thursday, 21 June 2018 at 23:34
> *To: *Joseph Berkovitz <joe@noteflight.com>
> *Cc: *Paul Adenot <padenot@mozilla.com>, "public-audio@w3.org Group" <
> public-audio@w3.org>
> *Subject: *Re: Auto-deploying the html version of the spec
> *Resent-From: *<public-audio@w3.org>
> *Resent-Date: *Thursday, 21 June 2018 at 23:33
>
>
>
> I think I have this all working, which you can see at
> https://github.com/rtoy/web-audio-api. In particular, .travis.yml,
> compile.sh and deploy.sh.  The scripts are still a bit messy, but I'll
> clean them up before trying them out on the official repo.
>
>
>
> So, when this lands, everyone will have to base the branches from the
> master; no work should be start from the gh-pages branch.  Since we're
> deploying to gh-pages, ideally, the gh-pages should only contain index.html
> and whatever necessary files are needed.  Not sure I'll get around to
> cleaning that up.  Not really necessary so we can take our time with that.
>
>
>
> However, one major blocker is that we need to create a deploy key for our
> repo.  This needs to be done by an owner.  I'll need an owner to do that
> for me. I can send you the instructions; it's not hard, but you need to
> have the right tools installed.
>
>
>
> On Thu, Jun 21, 2018 at 10:23 AM Joe Berkovitz <joe@noteflight.com> wrote:
>
> I've used Dom's technique successfully for the music notation CG, FYI. Let
> me know if you run into stuff.
>
>
> .            .       .    .  . ...Joe
>
> Joe Berkovitz
>
>
>
>
>
> On Wed, Jun 20, 2018 at 3:48 AM, Paul Adenot <padenot@mozilla.com> wrote:
>
> Thanks Raymond !
>
>
>
> Paul.
>
>
>
> On Tue, Jun 19, 2018 at 10:54 PM Raymond Toy <rtoy@google.com> wrote:
>
> Ever since switching to bikeshed, I've been manually updating index.html
> once in a while.  This gets tiring after a while.
>
>
>
> However, Domenic has posted a nice gist to auto-deploy to gh-pages using
> Travis CI. <https://gist.github.com/domenic/ec8b0fc8ab45f39403dd>
>
>
>
> This seems like a nice way, is spelled out in pretty good detail and
> doesn't use any personal tokens.
>
>
>
> To make things simpler (for me), we might have to put back the master
> branch.  Then all of your work and patches would need to go to the master
> branch instead of gh-pages.  gh-pages will only be for holding the
> generated index.html
>
>
>
> If we do this right, index.html will be automatically updated when
> index.bs is updated with no interactions from anybody.  Hopefully it will
> also only get updated if we don't introduce any new additional errors.
>
>
>
> I'll let you know if and when these changes happen.  Hopefully it will be
> mostly seamless except for possibly doing pull requests on the master
> branch instead of gh-pages.
>
>
>
>
>
>