Browse Source

update to builder tools and blog post

Lennart Weller 2 years ago
parent
commit
da08759da1
2 changed files with 11 additions and 14 deletions
  1. 2
    1
      .drone.yml
  2. 9
    13
      content/hugo-automatic-deploy.md

+ 2
- 1
.drone.yml View File

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

+ 9
- 13
content/hugo-automatic-deploy.md View File

@@ -27,8 +27,9 @@ The drone configuration lives in the root of the hugo-site git in the
27 27
 `.drone.yml` file and would look something like this:
28 28
 {{< highlight yaml >}}
29 29
 build:
30
-  image: r0/hugo
30
+  image: debian:stretch
31 31
   commands:
32
+    - apt-get update && apt-get -y install hugo python-pygments
32 33
     - hugo
33 34
 
34 35
 publish:
@@ -44,18 +45,7 @@ publish:
44 45
 drone.io internally uses docker containers for basically everything, which means
45 46
 images, plugins and so on are not limited to some predermined ones but can be
46 47
 basically anything. I am using a custom builder instance for hugo and an
47
-official drone publisher instance with `drone-rsync`. As not to rebuild the
48
-builder instance every time I made a small debian/testing based image which has
49
-the hugo binary preinstalled.
50
-
51
-The Dockerfile for creating the builder image is very simple and results in a
52
-quite small image:
53
-{{< highlight docker >}}
54
-#docker build --tag=r0/hugo builderfile
55
-FROM debian:stretch
56
-RUN apt-get update && apt-get -y install hugo python-pygments
57
-RUN rm -rf /var/lib/apt/lists/\*
58
-{{< /highlight >}}
48
+official drone publisher instance with `drone-rsync`. 
59 49
 
60 50
 On the server side I installed rssh via the usual channels then added a user for
61 51
 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
89 79
 automatically build, tested and then deployed to the server. In case you want to
90 80
 commit something without it being deployed you can simply add a `[ci skip]` to
91 81
 the commit message.
82
+
83
+* * *
84
+### Update (2016-10-14) ##
85
+Removed the usage of local builder tools as drone.io now seems to to only work
86
+with registries instead of locally available images. And running an additional
87
+docker registry just for the few updates we add to this blog seems pointless.

Loading…
Cancel
Save