LetsEncrypt with ACME on OpenWRT: Difference between revisions

Line 16:

In order to run the below command and have it 'install' in an 'industry standard' (AKA, non-OpenWRT) manner, the OPKG installation directory needs to be moved (and the run-acme file needs to be copied too)

* mv /usr/lib/acme /usr/lib/acme.OPKG - Move the OpenWRT OPKG installation to another directory

*mv /usr/lib/acme /usr/lib/acme.OPKG - Move the OpenWRT OPKG installation to another directory

* mkdir acme - Replace the acme directory

*mkdir acme - Replace the acme directory

* cp /usr/lib/acme.OPKG/run-acme /usr/lib/acme/ - Copy the OpenWRT proprietary run-acme file to it's original directory and path so the LuCI GUI can access it.

*cp /usr/lib/acme.OPKG/run-acme /usr/lib/acme/ - Copy the OpenWRT proprietary run-acme file to it's original directory and path so the LuCI GUI can access it.

Keep in mind when updating the Acme package(s) via OPKG, the acme.sh, run-acme, and dnsapi directory will be over written. But that's fine as the acme.sh.env file should be left in place.

Line 41:

Good, bash is found, so change the shebang to use bash as preferred.

OK

</syntaxhighlight>Contents of the /usr/lib/acme/acme.sh.env file created by the 'installation';<syntaxhighlight lang="text">

export LE_WORKING_DIR="/usr/lib/acme"

export LE_CONFIG_HOME="/etc/acme/config"

alias acme.sh="/usr/lib/acme/acme.sh --config-home '/etc/acme/config'"

</syntaxhighlight><br />

===Functionality===

@@ Line 16: / Line 16: @@
 In order to run the below command and have it 'install' in an 'industry standard' (AKA, non-OpenWRT) manner, the OPKG installation directory needs to be moved (and the run-acme file needs to be copied too)
-* mv /usr/lib/acme /usr/lib/acme.OPKG - Move the OpenWRT OPKG installation to another directory
+*mv /usr/lib/acme /usr/lib/acme.OPKG - Move the OpenWRT OPKG installation to another directory
-* mkdir acme - Replace the acme directory
+*mkdir acme - Replace the acme directory
-* cp /usr/lib/acme.OPKG/run-acme /usr/lib/acme/ - Copy the OpenWRT proprietary run-acme file to it's original directory and path so the LuCI GUI can access it.
+*cp /usr/lib/acme.OPKG/run-acme /usr/lib/acme/ - Copy the OpenWRT proprietary run-acme file to it's original directory and path so the LuCI GUI can access it.
 Keep in mind when updating the Acme package(s) via OPKG, the acme.sh, run-acme, and dnsapi directory will be over written.  But that's fine as the acme.sh.env file should be left in place.
@@ Line 41: / Line 41: @@
 Good, bash is found, so change the shebang to use bash as preferred.
 OK
+</syntaxhighlight>Contents of the /usr/lib/acme/acme.sh.env file created by the 'installation';<syntaxhighlight lang="text">
+export LE_WORKING_DIR="/usr/lib/acme"
+export LE_CONFIG_HOME="/etc/acme/config"
+alias acme.sh="/usr/lib/acme/acme.sh --config-home '/etc/acme/config'"
 </syntaxhighlight><br />
 ===Functionality===