From 4ac9c8d8aa260b67b61c41d6cf64f1b7a30b164a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stephan=20D=C3=B6rfler?= Date: Mon, 10 Feb 2020 10:54:28 +0100 Subject: [PATCH] added deployment and WIP to article --- content/blog/003-writing-articles/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/003-writing-articles/index.md b/content/blog/003-writing-articles/index.md index bef1186..28ba9a2 100644 --- a/content/blog/003-writing-articles/index.md +++ b/content/blog/003-writing-articles/index.md @@ -88,4 +88,4 @@ For now I only require two steps: 1. build the gatsby project 2. build the new docker image and push it to the registry -Then, the last required step is to update the running container to the new version. The event on which to react would be the upload to the registry. +Then, the last required step is to update the running container to the new version. The event on which to react would be the upload to the registry. There are some ways to handle this myself using webhooks, but as with the build trigger I decided to take a route a little more convenient: use [Watchtower](https://containrrr.github.io/watchtower). I tried watchtower before and don't feel comfortable blindly updating every container I run, so I [configure it to just watch the one blog container and update that automatically](https://containrrr.github.io/watchtower/container-selection/).