Allow a JSON file to be used for configuration

[mtwalsh]

Personal preference but I'd prefer to use a config.json file in the same directory as the Python script for configuration rather than the environment variable.

[tylrd]

Added a get_config() method that seems to work:

def get_config():
    aws_json = os.getenv(ENV_VAR)
    if aws_json is not None:
        return json.loads(aws_json)
    else:
        try:
            script_dir = os.path.dirname(os.path.abspath(__file__))
        except NameError:
            script_dir = os.path.dirname(os.path.abspath(sys.argv[0]))
        abs_file_path = os.path.join(script_dir, CONFIG_FILE)
        return json.loads(open(abs_file_path).read())

Commit is here: https://github.com/taylor-d/letsencrypt-aws/commit/7a8a67bede1b6623535061a333480cff369e74df. Need to do some testing before PR.

[mtwalsh]

Awesome, thanks for this!

[kbroughton]

+1
The docs might also explain how to pass json as an env variable.

[pugsley]

If you want to use a config.json file, create a simple wrapper like this in the same directory as letsencrypt-aws.py.

e.g. run.sh

#!/bin/bash
LETSENCRYPT_AWS_CONFIG=$(cat -) python letsencrypt-aws.py "$@"

Make it executable: chmod +x run.sh

Then you can use it like:

cat ./config.json | ./run.sh update-certificates

Then you can easily create multiple configs for each set of domains, e.g.

cat ./domain.com.json | ./run.sh update-certificates
cat ./otherdomain.net.json | ./run.sh update-certificates

This assumes run.sh and config.json are in the same directory as letsencrypt-aws.py (modify paths if they're not).

---

Here's a sample config.json file:

{
    "domains": [
        {
            "elb": {
                "name": "YOUR_ELB_NAME"
            },
            "hosts": ["HOST1.COM", "SUB.HOST1.COM"]
        }
    ],
    "acme_account_key": "file:///PATH/TO/YOUR/KEY"
}