WORKING_DIR in config file has no effect about getssl

A good point. it should work if "-w" is specified on the command line. if that's not defined, it assumes that the working directory is ~/.getssl and then uses that, there should be a way to put it in a config file though.

My challenge of logic, is how does it read from the config file, in the "WORKING_DIR" if that isn't defined on the command line, but is defined in the config file in "~/.getssl/getssl.cfg" (as it's reading it from "$WORKING_DIR/getssl.cfg" .. if that makes sense.

[deti-p]

You has two "working dirs". The WORKING_DIR and DOMAIN_DIR. In my mind they are the same.

But I can think of an environment where I use one dir for the account config file and other dir outside where the domains are stored in.

I would suggest to set the account-config file in ~/.getssl (default) or the "-w /dir".
If then someone defines WORKING_DIR in the account-config file to renew the WORKING_DIR, DOMAIN_DIR, ... in getssl after reading getssl.cfg.
Defining WORKING_DIR in the domail-config is useless, because the location was already created and can't be changed.

OK, I think I understand where you are coming from. I may need to define a new variable ( so that everything is backward compatible ).

WORKING_DIR and DOMAIN_DIR are slightly different.

WORKING_DIR is the top level directory, and then there is a different DOMAIN_DIR below that - for each domain.

How about if we had a variable DOMAIN_STORAGE .... which by default would be the same as WORKING_DIR ... but could be set in the "$WORKING_DIR/.getssl.cfg" and then all the domain data would be in $DOMAIN_STORAGE/$DOMAIN/

Would you want different $DOMAIN_STORAGE locations for different domains at all ?

[deti-p]

Perfect!

added in version 1.12 (I'll update the wiki / documentation).