Uh the only way I know how to link is with: #ipfs:matrix.org
But I don't know what that looks like on your end.
go-ipfs Github, and the Matrix/IRC room AFAIK.
'Name' : name,
'Description': desc
}
nftipfs = requests.post('https://ipfs.infura.io:5001/api/v0/add', files=files)
p = nftipfs
##nfthash = p['Hash']
print(p)
return render(request, 'nftdetails.html', {'NFTdesc': desc, 'NFTname': name})json.decoder.JSONDecodeError: Extra data: line 2 column 1
If I save some data and later retrieve it via the cid, what decoder must i use to decode the data to then parse it as json?
const block = Block.encoder({ "this": "is an object" }, "dag-cbor");
const data = block.encode();
const cid = await block.cid();
await ipfs.block.put(data, { cid: cid.toString() });
...
const block = await ipfs.block.get(cid.toString());
const data = new TextDecoder().decode(block.data); // Decoding with the default format of utf-8 leads to results that can't be parsed with JSON.parse
1 reply
1 reply
So you can always close the process running the critical section.
Try running
ipfs shutdownThis will close the running ipfs service node and hence clearing the critical section
Hey Everyone,
I am facing some major issues while setting up a private ipfs network on a bunch or raspberry pis,
- I have changed the apis, and gateway to 0.0.0.0
- I also added the bootstrap node (one of the raspberry pi is a bootstrap node)
- I have a local dns server for local network server process resolutions
No matter what I try, the peer table is empty.
An urgent help would be appreciated!
There seems to be a problem with running ipfs packages with other node js packages. In particular, any ipfs package (ipfs-core, ipfs-http-api) is throwing the following error:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in /path/to/project/core/node_modules/ipfs-core/package.jsonI found a discussion about a possible solution on github https://github.com/ipfs/js-ipfs/issues/4125#issuecomment-1146754121 but changing the "module" from "commonjs" to "esnext" opens up a bunch of other problems (in particular, I'm trying to run this within Hardhat and the Hardhat devs have stated there is no ES support on their short term roadmap.
There must be a way to get Hardhat and IPFS to work together but I've hit a roadblock and am unsure how to solve. Just wondering if anyone else has experienced this problem.
3 replies
Hi. What is the best practice for publishing IPNS content from more than one IPFS node? I want to have redundancy so that if one node fails, other can do it. It seems that the only way is to export/import keys manually. there is a API call for export/import keys but it seems not to work. Is there a way to programmatically create/share keys ?
ipfs/kubo#4240 : "If you'd like to implement ipfs key import/export, go ahead. We'll just have to restrict export to only running on the local node and not over the API"
Why not over the API?
