From d0fcd83ade04955d41206b20a5e343c523dc3be2 Mon Sep 17 00:00:00 2001 From: "Alex Ellis (OpenFaaS Ltd)" Date: Fri, 9 Feb 2024 16:05:53 +0000 Subject: [PATCH] Link to manual TCP tunnel Signed-off-by: Alex Ellis (OpenFaaS Ltd) --- blog/_posts/2024-02-09-the-homelab-tunnel-you-need.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/blog/_posts/2024-02-09-the-homelab-tunnel-you-need.md b/blog/_posts/2024-02-09-the-homelab-tunnel-you-need.md index 4ad1673..a9e9874 100644 --- a/blog/_posts/2024-02-09-the-homelab-tunnel-you-need.md +++ b/blog/_posts/2024-02-09-the-homelab-tunnel-you-need.md @@ -55,6 +55,8 @@ So let's create a TCP tunnel VM using our cloud of preference and a region close I'm going to use DigitalOcean for this example, but you can use any cloud you like. +The [inletsctl](https://github.com/inlets/inletsctl) tool can automate the VM creation and installation of the inlets-pro server for you. But if you like to do things the hard way, there's [also instructions for that](https://docs.inlets.dev/tutorial/dual-tunnels/). + ```bash inletsctl create --provider digitalocean \ --region lon1 \