Followup to this post.
I’ve encountered a few difficulties today, when my Wercker setup started failing while installing the few extra packages needed to deploy this blog.
I’m not sure exactly what happened, but I suspect that this is a case of the
debian docker image being cached too aggressively on Wercker, which made
packages installation more difficult (trying to access the wrong version or
something). Anyway, that was always a hack, and Docker images should be as
self-contained as possible.
Therefore, I built my own “box” (in Wercker lingo), that contains everything that’s needed to run the Hugo build, and GitHub pages deployment.
The image itself is very simple:
FROM ubuntu:15.10 MAINTAINER Yann Hodique <firstname.lastname@example.org> RUN apt-get update -q \ && DEBIAN_FRONTEND=noninteractive apt-get install -qy git openssh-client python-pygments curl \ && apt-get clean \ && rm -rf /var/lib/apt
On the blog side, it now looks like this:
box: sigma/blog-builder:v0.1.3 build: steps: - email@example.com after-steps: - slack-notifier: url: $SLACK_URL username: wercker deploy: steps: - firstname.lastname@example.org: token: $GIT_TOKEN domain: yann.hodique.info basedir: public
Next step will be to figure out why my first Alpine-based attempt ended up deploying something completely absurd…
Looks like there’s no end to yak shaving.