Publish erigonwatch ui for internal remote use #16
Conversation
|
This PR is for the QA department to remotely monitor the machines running the tests and those producing the prebuilt databases. We are already using it in our infrastructure, publishing it with nginx and securing access with OAuth2. |
|
@mriccobene why don't you use standard remote connection flow ? Have you tried https://testdiag.erigon.io ? |
| address = address.indexOf("/") >=0 ? address.substring(0, address.indexOf("/")) : address; | ||
| } | ||
|
|
||
| if (address === "127.0.0.1:6060" || address === "localhost:6060") isDefault = true; |
There was a problem hiding this comment.
This address may change as it setups by flag on diag cmd
|
@mriccobene @tosettil-polimi please check #17 I did some updates and also include changes which I think is required to support proxy. All what I did for it is added this two checks: |
|
Superseded by #17. Can be closed. |
The following changes are backward compatible and do not affect the normal development and usage of the erigontech/erigonwatch repository.
These modifications allow those who need it to publish the UI through a proxy so that it can be accessed remotely via a domain.
The changes enable the UI to detect whether it is being served on a domain rather than on localhost (or 127.0.0.1); in such cases, requests made to the Erigon node are directed to the same domain with the
/apiprefix, to be managed through a proxy.