From 0eb758ed6a734fa444226b5e667a1460cbdfe338 Mon Sep 17 00:00:00 2001 From: James Date: Sat, 22 May 2021 09:26:59 +0000 Subject: [PATCH] Update readme to justify the Cloudflare portion of this project --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 24680ef..5156d87 100644 --- a/README.md +++ b/README.md @@ -5,6 +5,8 @@ Tested with Terraform v0.13.6. This will deploy a mumble server (or murmur as it may be) onto a Vultr vc2-1c-1gb instance in the Sydney region, running Fedora 33 x64. +Upon deployment, the public IPv4 address of the instance that gets spun up will be inserted into a DNS record over at a Cloudflare hosted DNS zone. The case use for this is that users joining the server can simply remember or bookmark a specific hostname in their mumble client to connect to the server, with the server having the ability to be deployed & destroyed in an ephemeral manner only for when it's actually going to be used, so you're only incurring instance charges for when you're actually using it (when the Vultr instance is running). At present, Cloudflare do not charge for DNS hosting. You'd simply need a domain name setup inside Cloudflare, and you can forgo the costs of a reserved IP address over at Vultr, or using a DNS zone at the Vultr end. + ### Startup Script The startup script is located in two places for convenience. Because Vultr expects the script to be passed in Base64 encoding, we can use Terraform's `filebase64` functionality to automatically encode a file in base64 and pass it to this instance, like so: -- GitLab