github.com/vchain-us/vcn@v0.9.11-0.20210921212052-a2484d23c0b3/docs/user-guide/configuration.md (about) 1 # Configuration 2 3 By default, the `vcn` command line stores its config file (`config.json`) in a directory called `.vcn` within your `$HOME` directory. 4 > If the `STAGE` environment variable has been set, the default configuration directory can be different. See [environments](environments.md). 5 6 However, you can specify a different location for the config file via the `--vcnpath` command line option. For example: 7 8 ``` 9 vcn --vcnpath /path/to/your/config.json 10 ``` 11 12 <!-- The config file contains paths to keystore directories, and stores credentials of the current authenticated user. 13 14 `vcn` manages these files and directories and you should not modify them. 15 However, *you can modify* the config file to control where keys are stored. --> 16 17 ## Config file 18 19 ### Example of `config.json` 20 21 ``` 22 { 23 "currentcontext": "example@example.net", 24 "users": [ 25 { 26 "email": "example@example.net", 27 "token": "<authentication_bearer_token>" 28 ] 29 } 30 ] 31 } 32 ``` 33 34 ### Breakdown of `config.json`'s components 35 36 #### currentcontext 37 38 The property `currentcontext` holds the reference (user's email) to the current authenticated user. 39 40 #### users 41 42 The property `users` is an array of objects (one entry per user). Each object holds: 43 44 - `email` the email address that identifies a specific user 45 - `token` a bearer token used obtained by using `vcn login` 46 <!-- - `keystore` path to the actual directory that store private keys --> 47 48 <!-- ### Storing secret keys 49 50 Secret keys are stored as encrypted JSON files according to the Web3 Secret Storage specification. 51 See https://github.com/ethereum/wiki/wiki/Web3-Secret-Storage-Definition for more information. 52 53 You can modify the `keystore` property according to your needs in order to store secret keys in a different location. -->