Skip to content

Commit

Permalink
Merge pull request #181 from 0xScratch/patch-1
Browse files Browse the repository at this point in the history
Fixed typos and grammatical errors
  • Loading branch information
MoMannn authored May 23, 2024
2 parents 89aa991 + 2a67265 commit a21f7e1
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 8 deletions.
4 changes: 2 additions & 2 deletions build/2-storage-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -917,7 +917,7 @@ curl --location --request GET "https://api.apillon.io/storage/ipfs-cluster-info"

#### How to generate token programmatically

Apillon IPFS gateways accept [JWT token](https://jwt.io/), which can be creates using [jsonwebtoken](https://www.npmjs.com/package/jsonwebtoken) package.
Apillon IPFS gateways accept [JWT token](https://jwt.io/), which can be created using [jsonwebtoken](https://www.npmjs.com/package/jsonwebtoken) package.

The JWT sign method expects three (3) parameters:

Expand Down Expand Up @@ -1073,7 +1073,7 @@ curl --location --request GET "https://api.apillon.io/storage/buckets/:bucketUui

> API for creating a new IPNS record.
**Note: IPNS becomes accesible on the IPFS gateway when content with CID is published to it. To access IPNS content on the IPFS gateway, use `ipnsName`.**
**Note: IPNS becomes accessible on the IPFS gateway when content with CID is published to it. To access IPNS content on the IPFS gateway, use `ipnsName`.**

<CodeDiv>POST /storage/buckets/:bucketUuid/ipns</CodeDiv>

Expand Down
4 changes: 2 additions & 2 deletions build/3-hosting-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -402,7 +402,7 @@ curl --location --request PUT "https://sync-to-ipfs-queue.s3.eu-west-1.amazonaws
| Name | Description | Required |
| ----------- | ----------------------------------------------------------------------------------------------- | -------- |
| websiteUuid | Unique key of website. | true |
| sessionUuid | Session uuid, passed or recieved in [get URL for upload request](#post-storagebucketuuidupload) | true |
| sessionUuid | Session uuid, passed or received in [get URL for upload request](#post-storagebucketuuidupload) | true |

#### Possible errors

Expand Down Expand Up @@ -525,7 +525,7 @@ Review can take some time (up to 1 day) and if the website passes it, then the d

Websites with illegal/phishing content goes to status `101`. The project owner is notified via mail and most likely banned from Apillon platform.

To speed up deployment process, make sure that project has one of subscription packages.
To speed up deployment process, make sure that project has one of the subscription packages.

</div>
<div class="split_side">
Expand Down
8 changes: 4 additions & 4 deletions web3-services/7-web3-compute.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,15 +4,15 @@ In the world of web3 we have smart contracts that power some core backend logic

## NFT gated file access

Phala PHAT contracts are utilized to provide file encryption capabilities where there is no one that can access the encryption key. But a user with a specific NFT can utilized it. This results in a NFT gated fully encrypted file storage that is unstoppable in every way.
Phala PHAT contracts are utilized to provide file encryption capabilities where no one can access the encryption key. However, a user with a specific NFT can utilize it. This results in a NFT gated fully encrypted file storage that is unstoppable in every way.

Through Apillon you can deploy and configure the PHAT contract and use preexisting frontend templates to fully use the functionalities.

For using the NFT gated file access there are a few prerequisites:

1. You need to create a NFT collection. When deploying a PHAT contract you need to specify a NFT collection to which it is tied. And for each NFT you can either set the encrypted content that only the NFT owner will be able to access or make the NFT owner the one that can upload the file to storage.
2. You need a IPFS storage bucket. Any content uploaded via PHAT contract will need to be stored somewhere. For this you need to create an IPFS bucket (to make sure the content is distributed. Only encrypted content is ever stored).
2. You need a IPFS storage bucket. Any content uploaded via PHAT contract will need to be stored somewhere. For this, you need to create an IPFS bucket (to make sure the content is distributed. Only encrypted content is ever stored).

Which this prerequisites done you can then set this information and deploy you PHAT contract. Deployment and execution costs are handled by Apillon.
With these prerequisites done you can then set this information and deploy your PHAT contract. Deployment and execution costs are handled by Apillon.

You can create a PHAT contract either though the dashboard or via API / SDK.
You can create a PHAT contract either through the dashboard or via API / SDK.

0 comments on commit a21f7e1

Please sign in to comment.