From 785243799aa869cd21712b7a08827c9b2068ead5 Mon Sep 17 00:00:00 2001
From: jahway603 <jahway603@protonmail.com>
Date: Sun, 20 Nov 2022 22:18:10 -0500
Subject: [PATCH] add info on configuring nginx

---
 doc/examples/README.md | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/doc/examples/README.md b/doc/examples/README.md
index b8ca9ee..d8e6aa6 100644
--- a/doc/examples/README.md
+++ b/doc/examples/README.md
@@ -12,7 +12,19 @@ The [Hush Lightwalletd](https://git.hush.is/hush/lightwalletd/) can be configure
 ## With Nginx
 For Nginx specifics, refer to the [lightwalletd README](https://git.hush.is/hush/lightwalletd/src/branch/master/README.md) to setup your SSL cert config.
 
-Then you can use this [example shell script](run_lightwalletd_nginx.sh) to run lightwalletd with an nginx reverse proxy frontend. In the script you have to change the hostname and username before running it.
+1. Then you configure nginx for for a regular website & then run certbot to generate certs.
+
+1. Then use a block like this in your nginx config under the port 443 section:
+
+```
+location / {
+    # Replace localhost:9067 with the address and port of your gRPC server if     using a custom port
+    grpc_pass grpc://127.0.0.1:9067;
+}
+```
+
+1. Then you can use this [example shell script](run_lightwalletd_nginx.sh) to run lightwalletd with an nginx reverse proxy frontend. In the script you have to change the hostname and username before running it.
+
 
 ## No Web
 Here we run lightwalletd without any web servers (no nginx) and as a stand-alone service managing the SSL cert config internally. Use this [example shell script](run_lightwalletd_no-web.sh) to run lightwalletd stand-alone.