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

Add GLOBAL options #6

Closed
vasa-develop opened this issue May 19, 2019 · 1 comment
Closed

Add GLOBAL options #6

vasa-develop opened this issue May 19, 2019 · 1 comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature status/in-progress In progress

Comments

@vasa-develop
Copy link
Collaborator

vasa-develop commented May 19, 2019

Following Flags are supported in ipfs-cluster-ctl CLI.

 --host value, -l value         Cluster's HTTP or LibP2P-HTTP API endpoint (default: "/ip4/127.0.0.1/tcp/9094")
   --secret value                 cluster secret (32 byte pnet-key) as needed. Only when using the LibP2P endpoint
   --https, -s                    use https to connect to the API
   --no-check-certificate         do not verify server TLS certificate. only valid with --https flag
   --encoding value, --enc value  output format encoding [text, json] (default: "text")
   --timeout value, -t value      number of seconds to wait before timing out a request (default: 0)
   --debug, -d                    set debug log level
   --basic-auth value             <username>[:<password>] specify BasicAuth credentials for server that
requires authorization. implies --https, which you can disable with --force-http [$CLUSTER_CREDENTIALS]
   --force-http, -f  force HTTP. only valid when using BasicAuth
   --help, -h        show help
   --version, -v     print the version

Check which of these can be passed in the cluster initialization script(as headers).

@vasa-develop vasa-develop added kind/enhancement A net-new feature or improvement to an existing feature help wanted Seeking public contribution on this issue labels May 19, 2019
@hsanjuan
Copy link
Collaborator

hsanjuan commented May 22, 2019

The secret one is only for when we use http-tunneled-under-libp2p, which you can't use from Javascript.

The only relevant thing here for a js-api is basic auth (need to provide the basic auth header in the request).

@vasa-develop vasa-develop added status/in-progress In progress and removed help wanted Seeking public contribution on this issue labels May 22, 2019
vasa-develop added a commit that referenced this issue May 22, 2019
License: MIT
Signed-off-by: Vaibhav Saini <vasa@towardsblockchain.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature status/in-progress In progress
Projects
None yet
Development

No branches or pull requests

2 participants