-
Notifications
You must be signed in to change notification settings - Fork 748
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Siren Docs Upgrade #5979
Siren Docs Upgrade #5979
Conversation
This should probably target |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are some errors with the markdown linter. Run mdlint
from the Lighthouse root depository and it should automatically resolve some of the errors. Some others may need manual editing though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now. I just have a comment on the exiting without updating the withdrawal credentials. I wonder if it is worth to open an issue about it? There probably aren't that many users haven't updated their credentials, but there are some that still haven't. It could also be useful in testnet where the withdrawal credentials are of 0x00 type.
book/src/ui-faqs.md
Outdated
@@ -27,7 +27,7 @@ In the absence of a VPN, an alternative approach involves utilizing an SSH tunne | |||
|
|||
## 6. How do I connect Siren to Lighthouse via a ssh tunnel? | |||
|
|||
If you would like to access Siren beyond the local network (i.e across the internet), we recommend using an SSH tunnel. This requires a tunnel for 3 ports: `80` (assuming the port is unchanged as per the [installation guide](./ui-installation.md#docker-recommended)), `5052` (for beacon node) and `5062` (for validator client). You can use the command below to perform SSH tunneling: | |||
If you would like to access Siren beyond the local network (i.e across the internet), we recommend using an SSH tunnel. This requires a tunnel for 3 ports: `80` (assuming the port is unchanged as per the [installation guide](./ui-installation.md#building-from-docker-recommended)), `5052` (for beacon node) and `5062` (for validator client). You can use the command below to perform SSH tunneling: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the new release, do we need to change the port 80? The doc mentions it is on 3443 now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@antondlr can you help here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I'm gonna scrap the whole ssh tunnel idea, we no longer need that.
Siren is now supposed to run alongside your BN/VC, exposing a webapp that can be accessed from any browser.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we remove FAQ no. 6 about ssh tunnel if it is no longer relevant?
@antondlr , if you run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did another testing and this comment is from a user perspective:
How does a user ssh into a node and run Siren? I tested ssh into a node and started Siren with the flag --net=host
(got from @antondlr) , Siren started in the terminal, but I can't access SIren via the web browser of the client (I can access via the web browser of the server by just typing localhost
)
@Mergifyio queue |
🛑 The pull request has been removed from the queue
|
@Mergifyio refresh |
✅ Pull request refreshed |
@rickimoore - I think you need to merge the latest unstable |
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
b74761b
to
331e22f
Compare
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 9a53f4d |
Issue Addressed
Which issue # does this PR address?
Proposed Changes
Update siren docs
Additional Info
Added info about sirens new structure