Feature: Enable Letsencrypt staging enviorment

when LE_STAGING=TRUE is present in hestia.conf

- prevents hitting LE cert limits when testing

- cannot switch between PROD and STAGING and back, LE user profiles are bound to the URL (a cleanup on LE config is required to make this posibble)

Author: Lupul

bin/v-add-letsencrypt-domain

@@ -15,14 +15,18 @@ domain=$2
 aliases=$3
 mail=$4
 
-# LE API
-LE_API='https://acme-v02.api.letsencrypt.org'
-
 # Includes
 source $HESTIA/func/main.sh
 source $HESTIA/func/domain.sh
 source $HESTIA/conf/hestia.conf
 
+# LE API
+LE_API='https://acme-v02.api.letsencrypt.org'
+
+if [[ "$LE_STAGING" =~ ^(YES|TRUE)$ ]]; then
+    LE_API='https://acme-staging-v02.api.letsencrypt.org'
+fi
+
 # encode base64
 encode_base64() {
     cat |base64 |tr '+/' '-_' |tr -d '\r\n='

bin/v-add-letsencrypt-user

@@ -12,13 +12,17 @@
 # Argument definition
 user=$1
 
-# LE API
-LE_API='https://acme-v02.api.letsencrypt.org'
-
 # Includes
 source $HESTIA/func/main.sh
 source $HESTIA/conf/hestia.conf
 
+# LE API
+LE_API='https://acme-v02.api.letsencrypt.org'
+
+if [[ "$LE_STAGING" =~ ^(YES|TRUE)$ ]]; then
+    LE_API='https://acme-staging-v02.api.letsencrypt.org'
+fi
+
 # encode base64
 encode_base64() {
     cat |base64 |tr '+/' '-_' |tr -d '\r\n='