oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-26 19:49:26 +01:00
Code Releases Activity

Merge pull request #1269 from oceanprotocol/AnaLoznianu-patch-1

Browse Source 
Update ocean-cli
This commit is contained in:
Ana 2023-10-05 18:42:40 +03:00 committed by GitHub
commit cefc34d3cd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
developers/ocean-cli/consume.md
View File

@ -6,7 +6,7 @@ The process of consuming an asset is straightforward. To achieve this, you only
npm run cli download 'assetDID' 'download-location-path' npm run cli download 'assetDID' 'download-location-path'
``` ```
In this command, replace `assetDID`` with the specific DID of the asset you want to consume, and `download-location-path`` with the desired path where you wish to store the downloaded asset content In this command, replace `assetDID` with the specific DID of the asset you want to consume, and `download-location-path` with the desired path where you wish to store the downloaded asset content
Once executed, this command orchestrates both the **ordering** of a [datatoken](../contracts/datatokens.md) and the subsequent download operation. The asset's content will be automatically retrieved and saved at the specified location, simplifying the consumption process for users. Once executed, this command orchestrates both the **ordering** of a [datatoken](../contracts/datatokens.md) and the subsequent download operation. The asset's content will be automatically retrieved and saved at the specified location, simplifying the consumption process for users.

6
developers/ocean-cli/install.md
View File

@ -7,7 +7,7 @@ To get started with the Ocean CLI, follow these steps for a seamless setup:
Begin by cloning the repository. You can achieve this by executing the following command in your terminal: Begin by cloning the repository. You can achieve this by executing the following command in your terminal:
```bash ```bash
$ git clone https://github.com/oceanprotocol/ocean.js-cli.git $ git clone https://github.com/oceanprotocol/ocean-cli.git
``` ```
Cloning the repository will create a local copy on your machine, allowing you to access and work with its contents. Cloning the repository will create a local copy on your machine, allowing you to access and work with its contents.
@ -37,7 +37,7 @@ To successfully configure the CLI tool, two essential steps must be undertaken:
### Private Key Configuration ### Private Key Configuration
The CLI tool necessitates the configuration of the account's private key. This private key serves as the means by which the CLI tool establishes a connection to the associated wallet. It plays a crucial role in authenticating and authorizing operations performed by the tool. The CLI tool requires the configuration of the account's private key. This private key serves as the means by which the CLI tool establishes a connection to the associated wallet. It plays a crucial role in authenticating and authorizing operations performed by the tool.
```bash ```bash
export MNEMONIC="XXXX" export MNEMONIC="XXXX"
@ -50,7 +50,7 @@ Additionally, it is imperative to specify the RPC endpoint that corresponds to t
export RPC='XXXX' export RPC='XXXX'
``` ```
Furthermore, there are additional environment variables that can be configured to enhance the flexibility and customization of the environment. These variables include options such as the metadataCache URL and Provider URL, which can be specified if you prefer to utilize a custom deployment of Aquarius or Provider in contrast of the default settings. Moreover, you have the option to provide a custom address file path if you wish to use customized smart contracts or deployments for your specific use case. Remeber setting the next envariament variables is optional. Furthermore, there are additional environment variables that can be configured to enhance the flexibility and customization of the environment. These variables include options such as the metadataCache URL and Provider URL, which can be specified if you prefer to utilize a custom deployment of Aquarius or Provider in contrast to the default settings. Moreover, you have the option to provide a custom address file path if you wish to use customized smart contracts or deployments for your specific use case. Remember setting the next environment variables is optional.
```bash ```bash
export AQUARIUS_URL='XXXX' export AQUARIUS_URL='XXXX'