-
Notifications
You must be signed in to change notification settings - Fork 1.2k
jsipfs init
creates a repo that is not compatible with go-ipfs
#142
Comments
I already have a PR waiting for merge. :D ipfs/kubo#2497 |
Is it better to make the go-ipfs more loose? Or make js-ipfs more compliant? @whyrusleeping ? |
Good Q. Is |
@noffle if we had the DHT that go-ipfs implements, yes, it would be. |
making the go-ipfs daemon more loose on its requirements is good, but datastores are a mandatory thing, otherwise how will you store data? (the 'datastore' directory itself is not required, as long as you have a datastore of some kind) |
@whyrusleeping we have the datastore that stores blocks, not the datastore that stores DHT records (levelDB) |
theyre the same really, we just have a single datastore in go-ipfs. Its just a mounted datastore that stores certain key prefixes in one place and other key prefixes elsewhere. I'm going to be changing the datastore config code soon, heres a preview of what our current setup looks like in that new format: https://gist.github.com/whyrusleeping/0252846bc655632449b1 |
So, it sounds like we're for looser reqs + non-mandatory |
Tested this with latest |
awesome! :D thank you! |
I believe this is due go-ipfs does
datastore
(the LevelDB thing) checks, which we never implemented (since we didn't needed until we have the DHT going). Is there a way to create that folder eitherway so that ajs-ipfs
generated repo does work for a go-ipfs daemon? Simply dropping the same defaultdatastore
that go-ipfs generates should do the trick, not sure if there would be any concern there.@noffle since you made
js-ipfs init
, would you like to look at this one? Thank youThe text was updated successfully, but these errors were encountered: