-
Notifications
You must be signed in to change notification settings - Fork 4
Services used for storage
These are the services that we use for storage:
First of all, we store all the files (NFT images and music) on our local IPFS repository, see the page about IPFS. After we added the file to our local IPFS repository, we pin it at three outside services:
We are using my account ( ottpeter
) at the moment for storing the NFTs on Pinata. Unfortunately we are running out of the free plan limit (1GB), I'm not that much worried about that, because we are not solely relying on them. On the long run, we should update our plan, and probably we should use a dedicated account for this purpose. To use the pinning service of Pinata, we need an API key and secret, which is stored in a .env file on the backend directory, on the server. This is how our files that are uploaded on the Admin page looks like from the side of Pinata:
We are using my account ( ottpeter
) here as well. It's not clear to me what is there limit in the free plan. Here are some screenshots about the Infura UI:
Infura also uses API keys, the project_id and the secret is stored in the same .env file.
We are trying to pin the content on the Crust network three times, for redundancy. Here we are using a mnemonic for access. The mnemonic is in the same .env file. It's not obvious whether we still have credit in their system our not, although the pinning operations are going through. Most likely we have, but their UI is not very intuitive. https://app.crust.network/#/accounts
The code where the pinning happens is here