Skip to content
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

Implement additional connect parameters #71

Open
maarteNNNN opened this issue Oct 6, 2022 · 0 comments
Open

Implement additional connect parameters #71

maarteNNNN opened this issue Oct 6, 2022 · 0 comments
Assignees

Comments

@maarteNNNN
Copy link
Member

With ldpos-commander (CLI client), it doesn't seem to have a default IP/host when launching for the first time (or with fresh configs). It would be nice if it would default to capitalisk.com and the user can just leave empty and press enter to use that. (edited)
it should also prompt for the protocol secure (wss) or not (ws)
it should default to not secure ws though
encryption is not needed by default, transaction is signed anyway (cannot be tempered with) and ldpos-commander may be running on the machine as the capitalisk node if security is required (edited)
It should also prompt for the path
default to /socketcluster/
Maybe it should ask for hostname instead of IP so the user can provide a domain name instead of an IP address (edited)
and should default to capitalisk.com
as mentioned above

@maarteNNNN maarteNNNN self-assigned this Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant