update to builder tools and blog post

.drone.yml

@@ -1,6 +1,7 @@
 build:
-  image: ring0/hugo
+  image: debian:stretch
   commands:
+    - apt-get update && apt-get -y install hugo python-pygments
     - hugo
 
 publish:

content/hugo-automatic-deploy.md

@@ -27,8 +27,9 @@ The drone configuration lives in the root of the hugo-site git in the
 `.drone.yml` file and would look something like this:
 {{< highlight yaml >}}
 build:
-  image: r0/hugo
+  image: debian:stretch
   commands:
+    - apt-get update && apt-get -y install hugo python-pygments
     - hugo
 
 publish:
@@ -44,18 +45,7 @@ publish:
 drone.io internally uses docker containers for basically everything, which means
 images, plugins and so on are not limited to some predermined ones but can be
 basically anything. I am using a custom builder instance for hugo and an
-official drone publisher instance with `drone-rsync`. As not to rebuild the
-builder instance every time I made a small debian/testing based image which has
-the hugo binary preinstalled.
-
-The Dockerfile for creating the builder image is very simple and results in a
-quite small image:
-{{< highlight docker >}}
-#docker build --tag=r0/hugo builderfile
-FROM debian:stretch
-RUN apt-get update && apt-get -y install hugo python-pygments
-RUN rm -rf /var/lib/apt/lists/\*
-{{< /highlight >}}
+official drone publisher instance with `drone-rsync`. 
 
 On the server side I installed rssh via the usual channels then added a user for
 the upload. The login for the user is limited to the ssh key automatically
@@ -89,3 +79,9 @@ the Gogs repository and you are done. Every push to the repo should now be
 automatically build, tested and then deployed to the server. In case you want to
 commit something without it being deployed you can simply add a `[ci skip]` to
 the commit message.
+
+* * *
+### Update (2016-10-14) ##
+Removed the usage of local builder tools as drone.io now seems to to only work
+with registries instead of locally available images. And running an additional
+docker registry just for the few updates we add to this blog seems pointless.