New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More detailed usage #59
Comments
|
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
Finally, remember to use https://discuss.ipfs.io if you just need general support. |
|
This looks like a general support request. Try asking on https://discuss.ipfs.io as it'll be more visible to the community (nobody looks at closed GitHub issues). |
|
@yuhr if you want to run everything in memory, use const MemoryStore = require('interface-datastore').MemoryDatastoreconst ipfs = await IPFS.create({
repo: new Repo(`.ipfs/${nanoid()}`, {
storageBackends: {
root: MemoryStore,
// etc |
|
@aschmahmann Okay sorry, but I think this is rather an issue that the docs is lacking adequate information, though this could apply not only to this repo. I believe in-memory use case is pretty common for development environment, but the answer @achingbrain provided is not reachable from the readme of https://github.com/ipfs/js-ipfs. Though, let's move to https://discuss.ipfs.io, if you say nobody looks here. Thanks @achingbrain, but the general-support-request-like part of my question is still not resolved. Written here: https://discuss.ipfs.io/t/datastore-setup/10385 |
yuhr commentedFeb 9, 2021
•
edited
The section "Usage" in the readme is not fully illustrating how to use this module with
ipfs-core. Could you provide more information? How can I pass this module to "IPFS.create" API?I'm struggling to make IPFS work entirely in memory. My current setup is following (constructed according to https://github.com/ipfs/js-ipfs/blob/master/examples/custom-ipfs-repo/index.js), but it emits
OpenError: IO error: .ipfs/kptQGJNdBNgFcQxtixKUw/pins/LOCK: No such file or directory.The text was updated successfully, but these errors were encountered: