For the next level of automation, if you set up deploy keys and Travis CI, you can encrypt the private key using Travis’s tools, check the encrypted file into the repo, and then have this script run on Travis every time the master branch is changed (along with a snippet to decrypt the key for use).
For the next level of automation, if you set up deploy keys and Travis CI, you can encrypt the private key using Travis’s tools, check the encrypted file into the repo, and then have this script run on Travis every time the
masterbranch is changed (along with a snippet to decrypt the key for use).Yes exactly!
Or even better use the functionality that's already built into Travis CI:
TravisCI Github Pages Deployment
Oh, neat, thanks, I hadn’t seen that!
We might still have to use the keys, for organisational repositories, but it’s definitely something I’ll look at.
Yeah it's both pretty much the same so no real drawbacks either way.