3 ms·
Oh man, I could have sworn I saw commands like in (2) a while back but then just could not find them again the other day when I went looking, so I thought I'd i
by ashark 9y ago
Oh man, I could have sworn I saw commands like in (2) a while back but then just could not find them again the other day when I went looking, so I thought I'd imagined it. Great news. So the workflow there is to add the new file or directory, then link the hash you get back inside the collection you want to modify with the `object patch add-link` business? Not exactly ideal for direct use, but simple enough to be abstracted away in a not-insane script, looks like. Nice.
On (3), cool, I'd checked out a bit on following IPFS while waiting for private networks and filesystem-store to leave experimental status (here's where you tell me that's happened, too!) so I must have missed that. Good to know.
(4) was mostly my explaining why just having all the files individually in IPFS is really, really useless if you need to apply any tools to them that expect to operate on one or a small number of (possibly structured) directories, which describes an awful lot of tools that operate on large numbers of files, but that's moot given collection-modifying commands are available.
Thanks for the response.
- lgierth 9y agoAnd thanks for the feedback! :) We're actually thinking through the documentation overhaul right now (today and tomorrow) and large datasets are a top priority use case, so your post is really valuable. I'd say at this point private networks and the filestore are unlikely to change significantly, but we're not 100% satisfied with the respective test suites (and the docs, oh my) so it'll be a bit longer until they'll be elevated out of experimental status. About the object patch command, you can also call it through the HTTP API if that makes it easier. The CLI is essentially a 1:1 mapping of the HTTP API to a console command.