Improve standalone usability of Soledad Client
Currently, there are a number of pieces of information needed to instantiate Soledad Client that make its standalone use more difficult:
- information related to provider: user's uuid, server url, ca certificate file, authentication token.
- information on local paths: secrets path, local db path (and also blobs path that is not explicitelly given but derived from local db path).
If we remove the need to provide these pieces, then only the passphrase would be needed to use Soledad Client, which would make it easier to use it for general purpose local encrypted storage (i.e. not necessarily connected to a provider).
One initial proposal is:
-
make only the password be mandatory. -
use default
if no uuid is given. -
allow for empty server url, ca cert file, auth token, and avoid all network/sync if those are not given. -
use default paths if local paths are not given. -
improve documentation by including examples with the reactor.run()
call.
Edited by drebs