QmRpRyRX75cauJKMPSTHMrwJQpNCKLayQJScm29VMVZjkbbafybeibtwdweeyrgnjd2mh2aqihqwhdwwmkyyzgwm3r6p4kihhfgukhvbait’s possible to define names pointing to CIDs
latest.orcestra-campaign.org
brew install --cask ipfsbrew install --formula ipfs (you may need to run brew link ipfs)(it’s possible to run a node on kubo only, but slightly more complicated)
ipfs://<CID> and ipns://<name> may work, but can be problematic with CIDv0 (Qm...) because of case-sensitivityipfsspec for Pythonipfs:// and ipns:// links in common Python data packagespip install 'ipfsspec>=0.5.0'CID access:
import xarray as xr
xr.open_dataset("ipfs://QmQ5GpT44Hnssi4DbXPK6Z9LnYjwh3ujEJ3KPjQ45Km3qF",
engine="zarr")name access:
list directory
$ ipfs ls /ipns/latest.orcestra-campaign.org
QmbgNR1ZosE2dNRbca5GdqScB8pVh6yGjgG2nD5C3WT1bM - products/
QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn - raw/read a file
$ ipfs add --help
...
-r, --recursive bool - Add directory paths recursively.
-H, --hidden bool - Include files that are hidden.
--raw-leaves bool - Use raw blocks for leaf nodes.
...
Pinning a CID means that you instruct your node to:
Thus, if you want to keep some data on your machine, run
or
--progress shows some progress indicator--name: a label for you, which shows up in ipfs pin lsTo make data available for others, it’s good to pin data on a machine wich is more constantly connected than a laptop.
for ORCESTRA
latest.orcestra-campaign.org)Those lists are observed by IPFS nodes here on the campaign and in Hamburg, which will eventually fetch the referenced content and keep it stored.
It’s possible to access IPFS on levante at DKRZ.
You don’t have to run your own node, but you (currently have to create a file in your $HOME):
If you have this file, ipfsspec and Python access should work.