Jekyll is, no doubt, one of the best blog-aware static site generators available out there. While hosting the Jekyll site on GitHub Pages seems to be a very common practice, there are situations where we need the code source-controlled privately. GitHub charges for private repositories. BitBucket is the next go-to choice.
If the code is stored on BitBucket, GitHub pages may not be a possible hosting option, which brings us to Amazon Web Services. This gist is about having the code on BitBucket, having Wercker build the site and deploy it to AWS S3, and then having CloudFront deliver the site.
Here's a gist of how this is done:
- You add data to the code (basically Markdown files) as posts. These changes are pushed to BitBucket, the source control provider for the site.
- Wercker (a Docker-based continuous delivery platform) is triggered as soon as there's a push; it picks up the code from BitBucket.
- Wercker has two pipelines,
build
anddeploy
, which, of course, builds the site using Jekyll (on a R