-
Notifications
You must be signed in to change notification settings - Fork 1.2k
jsipfs init works but no results #286
Comments
If I'm running the daemon straight or with my own mount points it won't allow
|
It shouldn't be your peerId, but actually the folder hash that contains the Readme On the second set of questions, we haven't really tests js-ipfs on Windows, mainly because we don't have anyone that is completely focused on using the platform that can inform us how robust is the experience on Windows. Would you like to help us? :D Nevertheless, trying this, found a couple of bugs with init and cat, since they don't have the same behaviour as go-ipfs. //cc @nginnever @noffle
|
with jsipfs trying ipfs will say |
What's up with this
It calls a blank function? |
You have to 'implement it' in order to be able to do https://github.com/ipfs/js-ipfs-unixfs-engine/blob/master/src/importer.js#L61 |
From Duplex? |
Hey @MasterJames, is this still a issue, could you confirm? |
$ rm -r ~/.ipfs
$ ipfs init
initializing ipfs node at /Users/victor/.ipfs
generating 2048-bit RSA keypair...done
peer identity: QmdkKUnxKiDqEXd9QjPJGqUdXfgoqUFNZJTDQQCMtFJ4EV
to get started, enter:
ipfs cat /ipfs/QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme
$ rm -r ~/.ipfs
$ jsipfs init
$ |
Shows exactly same information as go-ipfs except for change of the cmd + cat so `ipfs cat` turns into `jsipfs files cat` instead. Ref: issue #286
Shows exactly same information as go-ipfs except for change of the cmd + cat so `ipfs cat` turns into `jsipfs files cat` instead. Ref: issue #286
Shows exactly same information as go-ipfs except for change of the cmd + cat so `ipfs cat` turns into `jsipfs files cat` instead. Ref: issue #286
Done in #475 |
when I run jsipfs init it does create the config so show will display the Identity.PeerId etc.
but it doesn't actually display what is shown in the demos as in results with the ipfs cat /ipfs/PeerId/readme
Maybe one needs some extra steps explained in the repo README to add files etc.?
When I add a with
files add NewFile.txt
it saysadded ID NewFile.txt
as expectedif I
files get /ipfs/ID
it sayserror EISDIR: illegal operation on a directory, open 'C:\WORK_FOLDER\IPFS\ipfs'
If I put "files get /ifps/ID/NewFile.txt" is says
error Non-base58 character
jsipfs ls ID
results in a blank line, while thefiles get
shows the directory in theEISDIR: illegal operation on a directory
error and if I look there is nothing there (after adding from outside). If I move the file in from the parent folder it was added from I see no change.Now If I
files add
from within the target folder in will create a directory with the same hash and the files is still there. Putting the file inside the folder named from the hash makes no difference to ls /ipfs/ID as it will always display blank.The text was updated successfully, but these errors were encountered: