Option to specify alternate config directory on first run

[alanhuang122]

When the bot is first run, it executes sopel/run_script.py at startup.
Said script is hardcoded to create ~/.sopel if it doesn't already exist.
Should there be an option to allow the user to specify an alternate directory to use?

This was observed on d9cfb41 running python sopel.py without prior configuration.

[freeboson]

@alanhuang122 are you thinking something like sopel -d ~/.sopel-alt?

[dgw]

@alanhuang122 It wasn't run_script.py, but the config helpers. Does 646f542 do what you're looking for?

[dgw]

Per #1404 (comment), I dug up the logs of the IRC conversation that led to this issue being opened in the first place. The words of the person who actually asked about this should give the best context:

<JZTech101> hi, how I can get sopel to install in a custom directory, along with all
            it's configs?
<alanhuang> JZTech101: there seems to be a homedir variable in [core]
<alanhuang> though it looks like sopel tries to create ~/.sopel initially if it doesn't
            exist(?)
<JZTech101> yes, yes it does. I was hoping for a non-code-editing solution? :/
<alanhuang> mmmmm
<alanhuang> let me see
<alanhuang> if you take an existing config file and add the homedir variable it works
<alanhuang> the only required variable seems to be [core] owner=
<JZTech101> required variable innthe config?
<alanhuang> yeah; it has defaults for server/port/other stuff *wince*
<alanhuang> nick, host, use_ssl, homedir, port, owner, channels are probably the bare
            minimum variables you want to specify to get things running
<JZTech101> awesome, thanks. I'll look into it when I gwt home, I'm at work
* alanhuang nods
<JZTech101> Also, I wouldn't worry too much about the defaults, it's likely a legacy
            thing they're too lazy to remove
<JZTech101> From when the bot's first roots
<alanhuang> opened an issue (though I don't expect much response) - might take a look
            and make a PR at some point

(Self-note: This is from /2018/01/11/freenode_%23sopel.log.gz)