Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Opening sequence in node or browser? #513

Closed
compsocial opened this issue Oct 7, 2016 · 2 comments
Closed

Opening sequence in node or browser? #513

compsocial opened this issue Oct 7, 2016 · 2 comments
Labels
help wanted Seeking public contribution on this issue

Comments

@compsocial
Copy link

I'm just getting started and I apologize for the beginner's question: What sequence of steps is necessary to get a functional ipfs instance running in Node and/or (but hopefully and) the browser? I can do the following:

var IPFS = require('ipfs')
var node = new IPFS()

as in README, but after that ... I'm not sure. I've been reading through the Orbit code, but from what I can tell it's connecting to a daemon running locally.

Can someone share a set of initialization steps ending with adding or getting a file? Would be nice to add that to the guide.

@interfect
Copy link

In Node at least it looks like you can crib some initialization from https://github.com/ipfs/js-ipfs/blob/c8dbf6ba16017103b29589bb6d4173f954b4325f/src/http-api/index.js where an IPFS node gets set up as part of the HTTP API setup.

@daviddias
Copy link
Member

Hey @compsocial, sorry for the delay, meanwhile we shipped examples to help people get started, hope they help, find them here: -> https://github.com/ipfs/js-ipfs/tree/master/examples

Let me know if you find any trouble :)

MicrowaveDev pushed a commit to galtproject/js-ipfs that referenced this issue May 22, 2020
test: add tests for cp, ls, mv, read outside of MFS
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Seeking public contribution on this issue
Projects
None yet
Development

No branches or pull requests

3 participants