Use Travis CI to auto update gh-pages (fix #296)

[alrra]

• Move figure-1.svg and the images from the gh-pages branch (namely: favicon.ico, figure-1.png & figure-2.png ) into img/, and update the build step to copy them into out/.
• Add a .travis.yml file with configurations to make Travis CI automatically update the content from the gh-pages branch with the content from out/ whenever a change is made in the master branch and the build is successful.

Outdated information was removed.

@bterlson Let me know if I can help you with something, or if I need to change anything.

[bterlson]

@alrra I will take a look at this tomorrow! But let me say, thanks so much for making this easy for me. It's pretty great you've given me a checklist (with screenshots!).

[annevk]

❤️

[mathiasbynens]

👍

In step 2.iii, if you append --add env.global to the command, it will automatically add the key to your .travis.yml file.

[alrra]

--add env.global to the command, it will automatically add the key to your .travis.yml file.

The reason why I didn't suggested it was because last night when I tested to see that everything works, --add env.global screwed up the .travis.yml file.

[bterlson]

This looks mostly good. I would prefer it if the images didn't have a different path in relative to spec.html in the different branches though. I like the img subfolder though, maybe we can just copy the entire folder to gh-pages and update spec.html to point to this location?

[michaelficarra]

It would make me uncomfortable that I was giving Travis and this npm module access to write to all public repos I own. In my own proposal, I use a deploy key that only has access to that one repo.

[alrra]

This looks mostly good. I would prefer it if the images didn't have a different path in relative to spec.html in the different branches though. I like the img subfolder though, maybe we can just copy the entire folder to gh-pages and update spec.html to point to this location?

@bterlson I will update my pull request.

deploy key that only has access to that one repo.

@michaelficarra Thanks for your comment! For some reason I thought there were similar in regards to access. I'll update the Travis script and the information from this pull request.

[michaelficarra]

Additionally, I would lock down the version of this dependency (and probably npm shrinkwrap) to protect against malicious updates.

[ljharb]

locking down dep versions doesn't give you any protection without shrinkwrap, and fails to communicate the intent to follow semver for updates when updating - it'd be best to use a ^ range, and then if you're concerned about updates, npm shrinkwrap --dev on top of that.

[Ms2ger]

What's this blocked on?

[michaelficarra]

Probably this: #309 (comment)

[bterlson]

Everything now auto-deploys!

[UltCombo]

Yayy! 👏