Merge pull request #1165 from oceanprotocol/feature/publish_with_arweave
Added arweave in the publishing with hosting services page
This commit is contained in:
Ana
GitHub
commit
4c70542f5c
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 60 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 113 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 231 KiB After Width: | Height: | Size: 66 KiB |
|
|
@ -1,30 +1,67 @@
|
|||
---
|
||||
title: Publish assets using hosting services
|
||||
description: Tutorial to publish assets using hosting services like AWS and Azure.
|
||||
description: Tutorial to publish assets using hosting services like Arweave, AWS, and Azure.
|
||||
---
|
||||
|
||||
# Publishing with Hosting Services
|
||||
## Overview
|
||||
|
||||
### Overview
|
||||
To publish on the Ocean Marketplace, publishers must first host their assets. It is up to the asset publisher to decide where to host the asset. For example, a publisher can store the content on decentralized storage like Arweave or choose a centralized solution like their AWS server, private cloud server, or other third-party hosting services. Through publishing, the information required to access the asset is encrypted and stored as a part of DDO on the blockchain. Buyers don't have access directly to this information, but they interact with the [Provider](https://github.com/oceanprotocol/provider#provider), which decrypts it and acts as a proxy to serve the asset. The DDO only stores the location of the file, which is accessed on-demand by the Provider. Implementing a security policy that allows only the Provider to access the file and blocks requests from other unauthorized actors is recommended. One of the possible ways to achieve this is to allow only the Provider's IP address to access the data. But, not all hosting services provide this feature. So, the publishers must consider the security features while choosing a hosting service.
|
||||
|
||||
To publish assets on the Ocean Marketplace, publishers must provide a link(an URL) to the file. It is up to the asset publisher to decide where to host the asset. For example, a publisher can store the content on their AWS server, private cloud server, or other third-party hosting services. Through publishing, the URL of the asset is encrypted and stored as a part of DDO on the blockchain. Buyers don't have access directly to the URL, but they interact with the Provider, which decrypts the URL and acts as a proxy to serve the asset. The DDO only stores the location of the file, which is accessed on-demand by the Provider. Implementing a security policy that allows only the Provider to access the URL and blocks requests from other unauthorized actors is recommended. One of the possible ways to achieve this is to allow only the Provider's IP address to access the URL. But, not all hosting services provide this feature. So, the publishers must consider the security features while choosing a hosting service.
|
||||
|
||||
On Ocean Marketplace, a publisher must provide the link to the asset during publish step in the field shown in the below image.
|
||||
On Ocean Marketplace, a publisher must provide the asset information during the publish step in the field shown in the below image. The information is a `link` for a classic URL, a `transaction ID` for a file stored on Arweave or a `CID` for an IPFS file.
|
||||
|
||||
|
||||
|
||||
### Hosting services
|
||||
|
||||
Publishers can choose any hosting service of their choice. The below section explains how to use commonly used hosting services with Ocean Marketplace.
|
||||
|
||||
Please use a proper hosting solution to keep your files.
|
||||
When using other systems (for example, `Google Drive`) that are not specifically
|
||||
designed for this use case, you risk not gaining traction. Systems such as `Google Drive`,
|
||||
include various virus checks and rate limiters that prevent the `Provider` to download the asset once it was purchased.
|
||||
⚠️ Note
|
||||
**Please use a proper hosting solution to keep your files.**
|
||||
Systems like `Google Drive` are not specifically designed for this use case. They include various virus checks and rate limiters that prevent the `Provider` to download the asset once it was purchased.
|
||||
|
||||
#### AWS
|
||||
## Decentralized hosting
|
||||
|
||||
AWS provides various options to host data and multiple configuration possibilities. Publishers are required to do their research and decide what would be the right choice. The below steps provide one of the possible ways to host data using AWS S3 bucket and publish it on Ocean Marketplace.
|
||||
### Arweave
|
||||
|
||||
[Arweave](https://www.arweave.org/) is a global, permanent, and decentralized data storage layer that allows you to store documents and applications forever. Arweave is different from other decentralized storage solutions in that there is only one up-front cost to upload each file.
|
||||
|
||||
**Step 1 - Get a new wallet and AR tokens**
|
||||
|
||||
Download & save a new wallet (JSON key file) and receive a small amount of AR tokens for free using the [Arweave faucet](https://faucet.arweave.net/). If you already have an Arweave browser wallet, you can skip to Step 3.
|
||||
|
||||
At the time of writing, the faucet provides 0.02 AR which is more than enough to upload a file.
|
||||
|
||||
If at any point you need more AR tokens, you can fund your wallet from one of Arweave's [supported exchanges](https://arwiki.wiki/#/en/Exchanges).
|
||||
|
||||
**Step 2 - Load the key file into the arweave.app web wallet**
|
||||
|
||||
Open [arweave.app](https://arweave.app/) in a browser. Select the '+' icon in the bottom left corner of the screen. Import the JSON key file from step 1.
|
||||
|
||||
|
||||
|
||||
**Step 3 - Upload file**
|
||||
|
||||
Select the newly imported wallet by clicking the "blockies" style icon in the top left corner of the screen. Select **Send.** Click the **Data** field and select the file you wish to upload.
|
||||
|
||||
|
||||
|
||||
The fee in AR tokens will be calculated based on the size of the file and displayed near the bottom middle part of the screen. Select **Submit** to submit the transaction.
|
||||
|
||||
After submitting the transaction, select **Transactions** and wait until the transaction appears and eventually finalizes. This can take over 5 minutes so please be patient. 
|
||||
|
||||
**Step 4 - Copy the transaction ID**
|
||||
|
||||
Once the transaction finalizes, select it, and copy the transaction ID.
|
||||
|
||||
|
||||
|
||||
**Step 5 - Publish the asset with the transaction ID**
|
||||
|
||||
|
||||
|
||||
## Centralized hosting
|
||||
|
||||
### AWS
|
||||
|
||||
AWS provides various options to host data and multiple configuration possibilities. Publishers are required to do their research and decide what would be the right choice. The below steps provide one of the possible ways to host data using an AWS S3 bucket and publish it on Ocean Marketplace.
|
||||
|
||||
**Prerequisite**
|
||||
|
||||
|
|
@ -44,12 +81,11 @@ Go to the AWS portal for S3: https://aws.amazon.com/s3/ and select from the uppe
|
|||
|
||||
**Create a bucket**
|
||||
|
||||
After logging into the new account, search for the available services and select `S3` type of
|
||||
storage.
|
||||
After logging into the new account, search for the available services and select `S3` type of storage.
|
||||
|
||||
|
||||
|
||||
In order to create a S3 bucket, choose `Create bucket`.
|
||||
To create an S3 bucket, choose `Create bucket`.
|
||||
|
||||
|
||||
|
||||
|
|
@ -59,8 +95,7 @@ Fill in the form with the necessary information. Then, the bucket is up & runnin
|
|||
|
||||
**Step 2 - Upload asset on S3 bucket**
|
||||
|
||||
Now, the asset can be uploaded by selecting the bucket name and choose `Upload`
|
||||
in the `Objects` tab.
|
||||
Now, the asset can be uploaded by selecting the bucket name and choosing `Upload` in the `Objects` tab.
|
||||
|
||||
|
||||
|
||||
|
|
@ -68,12 +103,11 @@ in the `Objects` tab.
|
|||
|
||||
Get the files and add them to the bucket.
|
||||
|
||||
The file is an example used in multiple Ocean repositories, and it can be
|
||||
found [here](https://raw.githubusercontent.com/oceanprotocol/c2d-examples/main/branin_and_gpr/branin.arff).
|
||||
The file is an example used in multiple Ocean repositories, and it can be found [here](https://raw.githubusercontent.com/oceanprotocol/c2d-examples/main/branin_and_gpr/branin.arff).
|
||||
|
||||
|
||||
|
||||
The permissions and properties can be set afterwards, for the moment keep them as default.
|
||||
The permissions and properties can be set afterward, for the moment keep them as default.
|
||||
|
||||
After selecting `Upload`, make sure that the status is `Succeeded`.
|
||||
|
||||
|
|
@ -81,39 +115,34 @@ After selecting `Upload`, make sure that the status is `Succeeded`.
|
|||
|
||||
**Step 3 - Access the Object URL on S3 Bucket**
|
||||
|
||||
By default, the permissions of accessing the file from S3 bucket are set to private.
|
||||
To publish an asset on the market, the S3 URL needs to be public.
|
||||
This step shows how to set up access control policies to grant permissions to others.
|
||||
By default, the permissions of accessing the file from the S3 bucket are set to private. To publish an asset on the market, the S3 URL needs to be public. This step shows how to set up access control policies to grant permissions to others.
|
||||
|
||||
**Editing permissions**
|
||||
|
||||
Go to the `Permissions` tab and select `Edit` and then uncheck `Block all public access`
|
||||
boxes to give everyone read access to the object and click `Save`.
|
||||
Go to the `Permissions` tab and select `Edit` and then uncheck `Block all public access` boxes to give everyone read access to the object and click `Save`.
|
||||
|
||||
If editing the permissions is unavailable, modify the `Object Ownership` by enabling the ACLs
|
||||
as shown below.
|
||||
If editing the permissions is unavailable, modify the `Object Ownership` by enabling the ACLs as shown below.
|
||||
|
||||
|
||||
|
||||
**Modifying bucket policy**
|
||||
|
||||
In order to have the bucket granted on public access, its policy needs to be
|
||||
modified likewise.
|
||||
To have the bucket granted public access, its policy needs to be modified likewise.
|
||||
|
||||
Note that the `<BUCKET-NAME>` must be chosen from personal buckets' dashboard.
|
||||
Note that the `<BUCKET-NAME>` must be chosen from the personal buckets dashboard.
|
||||
|
||||
```json
|
||||
```JSON
|
||||
{
|
||||
"Version": "2012-10-17",
|
||||
"Statement": [
|
||||
{
|
||||
"Sid": "Public S3 Bucket",
|
||||
"Principal": "*",
|
||||
"Effect": "Allow",
|
||||
"Action": "s3:GetObject",
|
||||
"Resource": "arn:aws:s3:::<BUCKET-NAME>/*"
|
||||
}
|
||||
]
|
||||
"Version": "2012-10-17",
|
||||
"Statement": [
|
||||
{
|
||||
"Sid": "Public S3 Bucket",
|
||||
"Principal": "*",
|
||||
"Effect": "Allow",
|
||||
"Action": "s3:GetObject",
|
||||
"Resource": "arn:aws:s3:::<BUCKET-NAME>/*"
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
|
|
@ -123,25 +152,21 @@ After saving the changes, the bucket should appear as `Public` access.
|
|||
|
||||
**Verify the object URL on public access**
|
||||
|
||||
Select the file from the bucket that needs verification and select `Open`. Now it should
|
||||
be able to download the file on personal system.
|
||||
Select the file from the bucket that needs verification and select `Open`. Now download the file on your system.
|
||||
|
||||
|
||||
|
||||
|
||||
**Step 4 - Get the S3 Bucket Link & Publish Asset on Market**
|
||||
|
||||
Now that the S3 endpoint has public access, the asset will be hosted successfully.
|
||||
|
||||
Go to [Ocean Market](https://market.oceanprotocol.com/publish/1) to complete the form
|
||||
for asset creation.
|
||||
Go to [Ocean Market](https://market.oceanprotocol.com/publish/1) to complete the form for asset creation.
|
||||
|
||||
Copy the `Object URL` that can be found at `Object Overview` from AWS S3 bucket
|
||||
and paste it in the `File` field from the form found at [step 2](https://market.oceanprotocol.com/publish/2) as it is illustrated below.
|
||||
Copy the `Object URL` that can be found at `Object Overview` from the AWS S3 bucket and paste it into the `File` field from the form found at [step 2](https://market.oceanprotocol.com/publish/2) as it is illustrated below.
|
||||
|
||||
|
||||
|
||||
#### Azure storage
|
||||
### Azure storage
|
||||
|
||||
Azure provides various options to host data and multiple configuration possibilities. Publishers are required to do their research and decide what would be the right choice. The below steps provide one of the possible ways to host data using Azure storage and publish it on Ocean Marketplace.
|
||||
|
||||
|
|
@ -193,22 +218,6 @@ Go to the Azure portal: https://portal.azure.com/#home and select `Storage accou
|
|||
|
||||
**Step 5 - Publish the asset using the generated link**
|
||||
|
||||
Now, copy and paste the link in the Publish page in the Ocean Marketplace.
|
||||
Now, copy and paste the link into the Publish page in the Ocean Marketplace.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue