Auto-deploying Jekyll via Github

If you are seeing this then everything worked fine and dandy. Woot.

It probably isn't hard to tell that this Blog is built using Jekyll (Octopress actually) and one of the things that I have always wanted to fix was how I deploy the site.

The workflow that I have used in the past is to:

Whilst this flow works pretty well, there are number of times where I don't have terminal access and even if I did, I don't have my public keys.

I need to be able to make changes on Github (or any other system that I can use to access my repository) and have them live on my site shortly after.

The new process I have now uses Github's WebHooks (they are amazing) to tell my blog to pull in the latest changes from the repository, build them and get them live. To integrate with Gihub's WebHooks I use the amazingly simple Github-Auto-Deploy with some modificiation from the original project and simple build script.

There really isn't anything to show you other than it just works. Now my deployment process is just a simple push up to Github. I even have the same ability to edit and test locally if I need to.

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.

I love to learn about what you are building, and how I can help with Chrome or Web development in general, so if you want to chat with me directly, please feel free to book a consultation.

I'm trialing a newsletter, you can subscribe below (thank you!)