From 185150552e47980f91a5a257906ccb9b478a4dce Mon Sep 17 00:00:00 2001
From: Derick M <58572875+TurtIeSocks@users.noreply.github.com>
Date: Fri, 23 Feb 2024 18:00:49 -0500
Subject: [PATCH] fix: favicon instructions

---
 server/src/configs/multi-domain-example/README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/server/src/configs/multi-domain-example/README.md b/server/src/configs/multi-domain-example/README.md
index 38ae998ff..45c3d25bf 100644
--- a/server/src/configs/multi-domain-example/README.md
+++ b/server/src/configs/multi-domain-example/README.md
@@ -70,4 +70,5 @@ pm2 start ecosystem.config.js
 - Be sure to view the `nginx` file to see how to set up the reverse proxy for the different domains
 - The domains do not have to be subdomains of each other, they can be whatever you want, they are just used to differentitate the different configs
 - The `NODE_CONFIG_ENV` var names should not contain `/` or `.`
-- The `NODE_CONFIG_ENV` value does not have to be related to the domain its representing. The URL for the map could be `https://www.my-super-map.com` and the `NODE_CONFIG_ENV` could be `applemap` or `orangemap` or `bananamap` or whatever you want, as long as you point the nginx reverse proxy to the correct instance of the app
\ No newline at end of file
+- The `NODE_CONFIG_ENV` value does not have to be related to the domain its representing. The URL for the map could be `https://www.my-super-map.com` and the `NODE_CONFIG_ENV` could be `applemap` or `orangemap` or `bananamap` or whatever you want, as long as you point the nginx reverse proxy to the correct instance of the app
+- Custom favicons can be set by putting the respective `{NODE_CONFIG_ENV}.ico` in the `public/favicon` folder
\ No newline at end of file