Skip to content

Commit 1851505

Browse files
committed
fix: favicon instructions
1 parent ef30f33 commit 1851505

File tree

1 file changed

+2
-1
lines changed
  • server/src/configs/multi-domain-example

1 file changed

+2
-1
lines changed

Diff for: server/src/configs/multi-domain-example/README.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -70,4 +70,5 @@ pm2 start ecosystem.config.js
7070
- Be sure to view the `nginx` file to see how to set up the reverse proxy for the different domains
7171
- 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
7272
- The `NODE_CONFIG_ENV` var names should not contain `/` or `.`
73-
- 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
73+
- 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
74+
- Custom favicons can be set by putting the respective `{NODE_CONFIG_ENV}.ico` in the `public/favicon` folder

0 commit comments

Comments
 (0)