From cd22c4ace2ffb53bc5733c262f9b81708122c4a7 Mon Sep 17 00:00:00 2001
From: Nico Schottelius <nico@nico-notebook.schottelius.org>
Date: Sun, 15 Dec 2019 00:04:42 +0100
Subject: [PATCH] +vm reference

---
 .../contents.lr                                          | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/content/u/blog/fully-automated-ssl-certificates-for-docker/contents.lr b/content/u/blog/fully-automated-ssl-certificates-for-docker/contents.lr
index d1a74c9..0e14aae 100644
--- a/content/u/blog/fully-automated-ssl-certificates-for-docker/contents.lr
+++ b/content/u/blog/fully-automated-ssl-certificates-for-docker/contents.lr
@@ -6,9 +6,9 @@ author: ungleich virtualisation team
 ---
 twitter_handle: ungleich
 ---
-_hidden: yes
+_hidden: no
 ---
-_discoverable: no
+_discoverable: yes
 ---
 abstract:
 Docker containers can now run fully https secured.
@@ -60,3 +60,8 @@ on the
 container](https://hub.docker.com/r/ungleich/nginx-letsencrypt-ipv6).
 Simply use the standard **FROM** statement in your dockerfile and
 enjoy a read-to-use-https-container.
+
+## Trying it out
+
+If you don't happen to have a host with an IPv6 network available, you
+can try it out on a VM on [IPv6onlyhosting.com](https://IPv6OnlyHosting.com].