From 03117dc32632e3dbba4af3cd7929f2e483db671e Mon Sep 17 00:00:00 2001 From: Colin Crossman Date: Tue, 12 Oct 2021 20:27:11 -0600 Subject: [PATCH] Update README.md for clarity It was unclear how to get the HEX of the TLS cert. Initially I had been trying to use openssl to export the hex of the signature, which was wrong. I finally realized that the xxd command was intended to be applied on the entire tls.cert file, and that worked. So I added this to clarify that aspect. --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 6b32adf..683e3e0 100644 --- a/README.md +++ b/README.md @@ -114,6 +114,11 @@ One click deployment with Heroku: You will need your LND address, the LND tls certificate (HEX) and the macaroon (HEX). +When getting the HEX of the TLS certificate, use `xxd -plain tls.cert | tr -d '\n'`. The TLS cert is located in the lnd directory: +* ~/umbrel/lnd/tls.cert on Umbrel +* /mnt/hdd/lnd/tls.cert on Raspiblitz +* Can also be located in ~/.lnd + [![Deploy on Heroku](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy?template=https://github.com/bumi/lnme) Here is a [Video Demo of the Heroku deployment](https://www.youtube.com/watch?v=hSFXhnLp_Rc)