aeb019f2b8
You can use it like this to launch all the test scripts in order: $ cd test $ make rm -r test-results *** t0010-basic-commands.sh *** ok 1 - current dir is writable ok 2 - ipfs version succeeds ok 3 - ipfs version output looks good ok 4 - ipfs help succeeds ok 5 - ipfs help output looks good # passed all 5 test(s) 1..5 ./test-aggregate-results.sh fixed 0 success 5 failed 0 broken 0 total 5 Or you can just run one test like this: $ make t0010-basic-commands.sh *** t0010-basic-commands.sh *** ok 1 - current dir is writable ok 2 - ipfs version succeeds ok 3 - ipfs version output looks good ok 4 - ipfs help succeeds ok 5 - ipfs help output looks good # passed all 5 test(s) 1..5 |
||
|---|---|---|
| blocks | ||
| blockservice | ||
| blockstore | ||
| cmd/ipfs | ||
| commands | ||
| config | ||
| core | ||
| crypto | ||
| daemon | ||
| diagnostics | ||
| exchange | ||
| fuse | ||
| Godeps | ||
| importer | ||
| merkledag | ||
| namesys | ||
| net | ||
| path | ||
| peer | ||
| pin | ||
| routing | ||
| server/http | ||
| test | ||
| unixfs | ||
| updates | ||
| util | ||
| .gitignore | ||
| .travis.yml | ||
| dev.md | ||
| doc.go | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
ipfs implementation in go. 
See: https://github.com/jbenet/ipfs
Please put all issues regarding IPFS design in the ipfs repo issues. Please put all issues regarding go IPFS implementation in this repo.
Install
Install Go 1.2+. Then:
go get github.com/jbenet/go-ipfs/cmd/ipfs
cd $GOPATH/src/github.com/jbenet/go-ipfs/cmd/ipfs
go install
NOTES:
gitand mercurial (hg) are required in order forgo getto fetch all dependencies.- Package managers often contain out-of-date
golangpackages. Compilation from source is recommended. - If you are interested in development, please install the development dependencies as well.
- WARNING: older versions of OSX FUSE (for Mac OS X) can cause kernel panics when mounting! We strongly recommend you use the latest version of OSX FUSE. (See https://github.com/jbenet/go-ipfs/issues/177)
Usage
ipfs - global versioned p2p merkledag file system
Basic commands:
add <path> Add an object to ipfs.
cat <ref> Show ipfs object data.
ls <ref> List links from an object.
refs <ref> List link hashes from an object.
Tool commands:
config Manage configuration.
version Show ipfs version information.
commands List all available commands.
Advanced Commands:
mount Mount an ipfs read-only mountpoint.
serve Serve an interface to ipfs.
Use "ipfs help <command>" for more information about a command.
Getting Started
To start using ipfs, you must first initialize ipfs's config files on your
system, this is done with ipfs init. See ipfs help init for information on
arguments it takes. After initialization is complete, you can use ipfs mount,
ipfs add and any of the other commands to explore!
NOTE: if you have previously installed ipfs before and you are running into
problems getting it to work, try deleting (or backing up somewhere else) your
config directory (~/.go-ipfs by default) and rerunning ipfs init.
Contributing
go-ipfs is MIT licensed open source software. We welcome contributions big and small! Please make sure to check the issues. Search the closed ones before reporting things, and help us with the open ones.
Guidelines:
- see the dev pseudo-roadmap
- please adhere to the protocol described in the main ipfs repo and paper.
- please make branches + pull-request, even if working on the main repository
- ask questions or talk about things in Issues or #ipfs on freenode.
- ensure you are able to contribute (no legal issues please-- we'll probably setup a CLA)
- run
go fmtbefore pushing any code - run
golintandgo vettoo -- some things (like protobuf files) are expected to fail. - if you'd like to work on ipfs part-time (20+ hrs/wk) or full-time (40+ hrs/wk), contact @jbenet
- have fun!
Todo
IPFS is nearing an alpha release. Things left to be done are all marked as Issues
Development Dependencies
If you make changes to the protocol buffers, you will need to install the protoc compiler.
License
MIT