From f8812501433b772b27a6fc601c190501562bf6fd Mon Sep 17 00:00:00 2001 From: Erik Winter Date: Mon, 11 Oct 2021 07:05:39 +0200 Subject: [PATCH] add project tags --- doc/httpmock_tutorial.adoc | 2 +- doc/logging-in-golang.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/httpmock_tutorial.adoc b/doc/httpmock_tutorial.adoc index be1261d..a24aab3 100644 --- a/doc/httpmock_tutorial.adoc +++ b/doc/httpmock_tutorial.adoc @@ -4,7 +4,7 @@ Erik Winter :kind: tutorial :public: yes :language: en -:tags: golang, tdd, http, rest +:tags: golang, tdd, http, rest, go-kit In general, when one wants to test the interaction of multiple services and systems, one tries to set up an integration test. This often involves spinning up some Docker containers and a docker-compose file that orchestrates the dependencies between them and starts the integration test suite. In other words, this can be a lot of work. diff --git a/doc/logging-in-golang.adoc b/doc/logging-in-golang.adoc index 52d2901..7016aff 100644 --- a/doc/logging-in-golang.adoc +++ b/doc/logging-in-golang.adoc @@ -4,7 +4,7 @@ Erik Winter :kind: tutorial :public: yes :language: en -:tags: golang +:tags: golang, go-kit The subject of logging comes up every now and then, in every group of developers. Apparently it is something to be opinionated about, like code formatting. Or to something complain about, like leaving off the cap of the toothpaste. If only there was a `go fmt` for logging. Or toothpaste.