Asceds default (overwritten by upgrades): /usr/lib/asceds/etc
Local setup (preserved between upgrades): /etc/asceds/

Executed in the following order:
local --> variables for asceds setup on the local computer 
site --> config variables common to the site, distributed by the certificate manager
hostconf --> config variables describing the host OS and services
certbot --> config variables for certbot management

If some clients need special kinds of certificates (e.g., IGTF) that are obtained
through a different ACME account, a host asceds-certbot.conf configuration file 
placed in /etc/asceds/home/(client)/ takes precedence over the server configuration.
That certbot account needs to be registered separately.
However, scripts like asceds-authorized-domains or asceds-certmanager-setup
act on the server configuration file.
Currently, the host configuration file for the host ACME account needs to be 
maintained by hand on the server.

First, all the default config files are sourced,
then the local setup to overwrite the default values.

Scripts set sourcing order in ${ASCEDSCONF}.
Since asceds-certbot.conf is readable only by root, it should be sourced 
only by scripts that run as root.
Changing values is safely done throuth asceds-utils/asceds-refresh-var 
Refreshing is done through asceds-utils/asceds-source-etcconf

****************************************************************
asceds-site.conf:

# alarm email address
ALARM=""
# certificate manager hostname 
ASCEDSCRTMGR=""
# wget -> for self signed certificates on the certificate manager,
# add `--no-check-certificate' to wget 
WGET='/usr/bin/wget'
# asceds ssh public key
ASCEDSSSHPUBKEY=''
# list of encryption algorithms (rsa,ecdsa)
ASCEDSENCLIST="rsa"

