From e2d787166e00b92d812a2f05bcd216dd90158b02 Mon Sep 17 00:00:00 2001 From: Wesley Moore Date: Sat, 15 Jan 2022 10:47:51 +1000 Subject: [PATCH] Update Alpine infra post to note move to lego --- v1/.ruby-version | 2 +- v1/README.mkdn | 13 +++++++++++++ .../2019/02/alpine-linux-docker-infrastructure.md | 6 ++++++ .../2019/02/alpine-linux-docker-infrastructure.yaml | 2 +- 4 files changed, 21 insertions(+), 2 deletions(-) diff --git a/v1/.ruby-version b/v1/.ruby-version index e70b452..a603bb5 100644 --- a/v1/.ruby-version +++ b/v1/.ruby-version @@ -1 +1 @@ -2.6.0 +2.7.5 diff --git a/v1/README.mkdn b/v1/README.mkdn index 7ba7e62..ccd6fa4 100644 --- a/v1/README.mkdn +++ b/v1/README.mkdn @@ -21,3 +21,16 @@ Set updated_at on a post in vim: Trim CLI screenshots: convert *.png -set filename:name '%t' -background white -splice 0x1 -background white -splice 0x1 -trim +repage -chop 0x1 '%[filename:name].png' + +Setup +----- + + frum install (then cd ..; cd -) + gem install bundler --no-doc --version '~> 1' + bundle install + +Building and Deployment +----------------------- + +* Build with: `nanoc co` +* Deploy with: `nanoc deploy` diff --git a/v1/content/technical/2019/02/alpine-linux-docker-infrastructure.md b/v1/content/technical/2019/02/alpine-linux-docker-infrastructure.md index 87fbe97..f147540 100644 --- a/v1/content/technical/2019/02/alpine-linux-docker-infrastructure.md +++ b/v1/content/technical/2019/02/alpine-linux-docker-infrastructure.md @@ -198,6 +198,11 @@ use the DNS validation method (`certbot` can do this too). This requires a DNS provider that has an API so the client can dynamically manipulate the records. I looked through the large list of supported providers and settled on [LuaDNS]. +**Update 11 May 2020:** I contributed support for LuaDNS to [lego] and replaced +`acme.sh` with it. The motivation was that I never got auto-renewal working +with `acme.sh`. Turns out it was nothing to do with `acme.sh` but the exercise +in moving to `lego` made me discover and fix the problem. + LuaDNS has a nice git based workflow where you define the DNS zones with small Lua scripts and the records are published when you push to the repo. They also have the requisite API for `acme.sh`. You can see my DNS repo at: @@ -425,3 +430,4 @@ Next Post: [A Coding Retreat and Getting Embedded Rust Running on a SensorTag](/ [Varnish]: https://varnish-cache.org/ [Vultr]: https://www.vultr.com/?ref=7903263 [WebPageTest]: https://www.webpagetest.org/ +[lego]: https://github.com/go-acme/lego diff --git a/v1/content/technical/2019/02/alpine-linux-docker-infrastructure.yaml b/v1/content/technical/2019/02/alpine-linux-docker-infrastructure.yaml index c66af16..c4e1288 100644 --- a/v1/content/technical/2019/02/alpine-linux-docker-infrastructure.yaml +++ b/v1/content/technical/2019/02/alpine-linux-docker-infrastructure.yaml @@ -4,7 +4,7 @@ extra: My story of replacing three servers, across two countries, running two op kind: article section: technical created_at: 2019-02-28 09:45:00.000000000 +11:00 -updated_at: 2019-03-13T20:37:45+11:00 +updated_at: 2022-01-15T10:35:39+10:00 keywords: - docker - linux