If you’re familiar with both Hugo and Wercker, all you require to know is that the step is called
arjen/hugo-build and you can easily find it in the Wercker steps repository.
Short Wercker introduction
Wercker is a continuous integration tool. This basically means you can make it do all the hard and boring work for you that you don’t really want or need to do.
It does this by using steps. These steps can be anything from running jshint to building entire applications.
What does this step do?
The step I built is a fairly simple one. It will download the specified version of Hugo, and then build your site using that version. In fact, if you look at the source code you can clearly see that it downloads a version of Hugo, unpacks it, and then runs the build command from that binary.
Why would I want to use this?
Because it’s easier. As you can see in the examples below, it makes deployments to GitHub Pages or any other type of site a lot easier. It also means that you don’t have to be on your computer if you want to post an article as you can just push up your latest Markdown file to GitHub or Bitbucket and everything else is handled for you.
What options are there for using it?
You can specify 3 different things:
The version of Hugo
This one is fairly obvious, and I would recommend that you specify your version as otherwise you might run into a problem when the next version of Hugo is released and changes things around that you don’t expect.
If you use a theme you can specify this in the Wercker configuration as well.
Any other flags
If you have any other flags you wish to use with the hugo command you can provide these as a single line in the config.
The following two examples are from the configuration for this site as well as my other travel log site.
This shows an example of building the site with my step, and then deploying it to Amazon S3.
box: wercker/default build: steps: - arjen/hugo-build: version: 0.12 deploy: steps: # Execute the s3sync deploy step, a step provided by wercker - s3sync: key_id: $AWS_ACCESS_KEY_ID key_secret: $AWS_SECRET_ACCESS_KEY bucket_url: $AWS_BUCKET_URL source_dir: public/
This example builds the site once again using my step, but the deployment is to GitHub Pages instead.
box: wercker/default build: steps: - arjen/hugo-build: version: 0.12 deploy: steps: - firstname.lastname@example.org: token: $GIT_TOKEN domain: www.arjen.eu basedir: public
Using a theme and flags
The same example as above, but this time using a theme and optional flags
box: wercker/default build: steps: - arjen/hugo-build: version: 0.12 theme: redlounge flags: --disableSitemap=true deploy: steps: - email@example.com: token: $GIT_TOKEN domain: www.arjen.eu basedir: public