You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This change is required for containerised versions to run properly.
Adds:
--ws-external
--rpc-external
USAGE:
polkadot [FLAGS] [OPTIONS] [SUBCOMMAND]
FLAGS:
--dev Run in development mode; implies --chain=dev --validator --key Alice
-h, --help Prints help information
--light Run in light client mode
--no-telemetry Should not connect to the Polkadot telemetry server (telemetry is on by default on global
chains)
⥤ --rpc-external Listen to all rpc interfaces (Default is local)
-t, --telemetry Should connect to the Polkadot telemetry server (telemetry is off by default on local chains)
--validator Enable validator mode
-V, --version Prints version information
⥤ --ws-external Listen to all web socket interfaces (Default is local)
<...>
Yes, I can understand.
If we go safety first, we will have less nodes (missing out all those docker nodes).
If we take this fix without #494 we increase the risks. I think this is however acceptable for a PoC stage with only a testnet. I would gladly take a look at #494 but I have no idea how long it would take me, I have no clue how this was done in parity.
Maybe we can try to avoid too many configuration flags for RPC servers for now? Can live with --expose or --external-rpc flag that sets the interfaces to 0.0.0.0? I'd be in favor of something more clever for the future (either the proxy or configuration files). I don't think that selecting a specific interface to listen on is super useful anyway - usually it's just localhost or "external/all"
The reason will be displayed to describe this comment to others. Learn more.
I believe there is no point in running RPC externally but not WS, would merge the two flags to avoid clutter in CLI help.
In the future we will most likely run HTTP & WS transport on the same port anyway, so maybe it will be a good opportunity to merge the two options as well.
The reason will be displayed to describe this comment to others. Learn more.
I did not want to be too pushy here and let for now the users decide. That allows at the moment a user to 'open up' WS while keeping RPC only local only. It may be better security-wise for now.
* master:
README: fixed typo in docker run command (#518)
Merge *_at methods. (#515)
New flags to listen to all interfaces (#495)
If contract reaches max depth, return Err (#503)
Some networking cleanups (#504)
Derivable Encode & Decode (#509)
substrate: return Option in all storage related RPC methods (#510)
Build with locked Cargo.lock on CI (#514)
Place call data into a newly allocated pages (#502)
* examples: Use tokio instead of std async
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
* test-runtime: Use tokio instead of std async
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
* subxt: Use tokio instead of std async
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
* examples: Use only necessary tokio features
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current version listens only on 127.0.0.1.
This change is required for containerised versions to run properly.
Adds:
--ws-external--rpc-external