@@ -89,6 +89,14 @@ After the token is generated, create an rc file with the following content:
89
89
Note: you could use ` ncu-config ` to configure these variables, but it's not
90
90
recommended to leave your tokens in your command line history.
91
91
92
+ If you have ` gpg ` installed and setup on your local machine, it is recommended
93
+ to store an encrypted version of this file:
94
+
95
+ ``` console
96
+ $ gpg --default-recipient-self --encrypt ~ /.ncurc
97
+ $ rm ~ /.ncurc
98
+ ```
99
+
92
100
### Setting up Jenkins credentials
93
101
94
102
The ` git-node ` and ` ncu-ci ` commands need to query the Node.js Jenkins API for
@@ -104,8 +112,9 @@ To obtain the Jenkins API token
104
112
3 . Enter an identifiable name (for example, ` node-core-utils ` ) for this
105
113
token in the inbox that appears, and click ` GENERATE ` .
106
114
4 . Copy the generated token.
107
- 5 . Add it into your ` ncurc ` file (` ~/.ncurc ` or ` $XDG_CONFIG_HOME/ncurc ` )
108
- with ` jenkins_token ` as key, like this:
115
+ 5 . Add it into your ` ncurc ` file (` ~/.ncurc ` or ` $XDG_CONFIG_HOME/ncurc ` , or
116
+ ` ~/.ncurc.gpg ` or ` $XDG_CONFIG_HOME/ncurc.gpg ` ) with ` jenkins_token ` as key,
117
+ like this:
109
118
110
119
``` json
111
120
{
@@ -125,6 +134,7 @@ Put the following entries into your
125
134
```
126
135
# node-core-utils configuration file
127
136
.ncurc
137
+ .ncurc.gpg
128
138
# node-core-utils working directory
129
139
.ncu
130
140
```
0 commit comments