From 78e8cbd0cc8b707bca4be0ad0bedc99c969c3dc8 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 18 Mar 2023 13:17:32 +0200 Subject: Update content for html --- gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.html | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.html') diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.html b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.html index b6c2ff4c..3d67d34f 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.html +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.html @@ -599,9 +599,8 @@ rex commons

ACME and Let's Encrypt greatly help reduce recurring manual maintenance work (creating and renewing certificates). Furthermore, all the certificates are free of cost! I love to use OpenBSD and Rex to automate all of this.

OpenBSD suits perfectly here as all the tools are already part of the base installation. But I like underdogs. Rex is not as powerful and popular as other configuration management systems (e.g. Puppet, Chef, SALT or even Ansible). It is more of an underdog, and the community is small.

Why re-inventing the wheel? I love that a Rexfile is just a Perl DSL. Also, OpenBSD comes with Perl in the base system. So no new programming language had to be added to my mix for the configuration management system. Also, the acme.sh shell script is not a Bash but a standard Bourne shell script, so I didn't have to install an additional shell as OpenBSD does not come with the Bash pre-installed.

-E-Mail your comments to hi@paul.cyou :-)
-More entries
-Back to the main site
+

E-Mail your comments to hi@paul.cyou :-)

+Back to the main site

Generated with Gemtexter | served by OpenBSD/httpd(8) | -- cgit v1.2.3