Skip to content

Commit 6e0ace9

Browse files
committed
doc: Add example "lightning directory" location for gRPC certs.
1 parent 2889bd9 commit 6e0ace9

File tree

1 file changed

+2
-2
lines changed
  • doc/developers-guide/app-development

1 file changed

+2
-2
lines changed

doc/developers-guide/app-development/grpc.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ openssl x509 -req -CA ca.pem -CAkey ca-key.pem \
140140

141141

142142

143-
This will finally create the `server.pem` file, signed by the CA, allowing you to access the node through its real domain name. You can now move `server.pem` and `server-key.pem` into the lightning directory, and they should be picked up during the start.
143+
This will finally create the `server.pem` file, signed by the CA, allowing you to access the node through its real domain name. You can now move `server.pem` and `server-key.pem` into the lightning directory (ex. `<lightning-dir>/bitcoin` for `mainnet`), and they should be picked up during the start.
144144

145145
#### Generating custom certificates using SANs (Subject Alternative Names)
146146

@@ -192,4 +192,4 @@ openssl x509 -req -CA ca.pem -CAkey ca-key.pem -in server.csr -out server.pem -d
192192

193193

194194

195-
As above, generate the new server certificate, but this time with the `SAN` configuration. Copy `server.pem` and `server-key.pem` into the certificates location and restart the service to take effect.
195+
As above, generate the new server certificate, but this time with the `SAN` configuration. Copy `server.pem` and `server-key.pem` into the certificates location (ex. `<lightning-dir>/bitcoin` for `mainnet`) and restart the service to take effect.

0 commit comments

Comments
 (0)