I’m working on distributing blockstack with the native macOS app. As part of this, I’d like to make sure that blockstack’s configuration gets installed in a platform appropriate location inside ~/Library (like other bundle-installed macOS apps)
It looks like we can currently set the location of the configuration file using the
BLOCKSTACK_CLIENT_CONFIG environment variable.
BLOCKSTACK_CLIENT_CONFIG=/Users/larry/my-blockstack-config/client.ini creates that config file and a few other files in that same directory.
It seems inconsistent to be able to specify an arbitrary name for
client.inibut not of the other files.
It doesn’t seem to be possible to change the location of
BLOCKSTACK_METADATA_DIRwithout editing the configuration file after it is created.
BLOCKSTACK_METADATA_DIRis hardcoded to
BLOCKSTACK_CLIENT_CONFIGcreates another directory.
I’d expect that metadata would default to being in a subdirectory of the client configuration directory.
Would it make more sense to instead have an environment variable or command line option to specify a configuration directory and have the layout of files and subdirectories within that folder be consistent? (or am I using this wrong?)
What do you think, @jude?