Update instructions

This commit is contained in:
Prathamesh Musale 2023-04-25 18:27:01 +05:30
parent 4260fd5734
commit c61fa2a3f4
2 changed files with 2 additions and 2 deletions

View File

@ -162,7 +162,7 @@ Check watcher container logs to get multiaddr advertised by the watcher's relay
## Web App ## Web App
To be able to connect to the relay node from remote peers, it needs to be publicly reachable. To be able to connect to the relay node from remote peers, it needs to be publicly reachable.
Configure your website with SSL and the `https` traffic forwarded as: Configure your website with SSL and the `https` traffic reverse proxied as:
* `/graphql` to port `3001` (watcher GQL endpoint) * `/graphql` to port `3001` (watcher GQL endpoint)
* `/` to port `9090` (relay node) * `/` to port `9090` (relay node)

View File

@ -97,7 +97,7 @@ To monitor the running container:
Note: For opening an invite link on this deployed app, replace the URL part before `/#` with `http://localhost:3004` Note: For opening an invite link on this deployed app, replace the URL part before `/#` with `http://localhost:3004`
For example: `http://localhost:3004/#/members?invitation=XYZ` For example: `http://localhost:3004/#/members?invitation=XYZ`
In order to host the app using a public domain, configure your website with SSL and the `https` traffic forwarded to port `3004`. In order to host the app using a public domain, configure your website with SSL and `https` traffic reverse proxied to port `3004`.
For example, a Nginx configuration for domain `my-mobymask-app.example.com` would look something like: For example, a Nginx configuration for domain `my-mobymask-app.example.com` would look something like: