jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-15 21:36:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add missing period

Browse Source
This commit is contained in:
Fabian Affolter 2017-07-18 21:43:49 +02:00
parent a959d384b7
commit a3198ce772
No known key found for this signature in database
GPG Key ID: DDF3D6F44AAB1336
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
source/_docs/configuration/secrets.markdown
View File

@ -46,20 +46,22 @@ When you start splitting your configuration into multiple files, you might end u
To see where secrets are being loaded from you can either add an option to your `secrets.yaml` file or use the `check_config` script.
*Option 1*: Print where secrets are retrieved from to the Home Assistant log by adding the following to `secrets.yaml`:
```yaml
logger: debug
```
This will not print the actual secret's value to the log.
*Option 2*: View where secrets are retrieved from and the contents of all `secrets.yaml` files used, you can use the `check_config` script from the command line:
```bash
hass --script check_config --secrets
```
This will print all your secrets
This will print all your secrets.
### {% linkable_title Storing passwords in a keyring managed by your OS %}
Using [Keyring](https://github.com/jaraco/keyring) is an alternative way to `secrets.yaml`. They can be managed from the command line via the keyring script.
Using [Keyring](https://github.com/jaraco/keyring) is an alternative way to `secrets.yaml`. They can be managed from the command line via the `keyring` script.
```bash
$ hass --script keyring --help