Go to file
Natalie Villasana 1a06c2b0c7 adding grpc interface to network state (#33)
* adds proto files for netstate crud

* moves netstate grpc client lib into pkg/netstate where grpc netstate service is defined

* starts adding grpc client and server tests

* moves creation of grpc server into cmd/netstate/main.go, removes pkg/netstate/service.go, adds more client testing

* changed all 'Path' and 'Value' fields from strings to bytes, updated tests

* changes Get and Delete in proto file to receive 'requests' instead of 'file paths', adds tests for Get, List, and Delete

* changes netstate-routes to get 'fileValue' bytes not 'fileInfo'

* adds example rpc client in 'examples' and adds more specific debug logs

* adds readmes for netstate rpc services and updates netstate-routes
2018-05-14 18:31:26 -06:00
api keep 2018-04-06 12:36:55 -04:00
assets keep 2018-04-06 12:36:55 -04:00
build keep 2018-04-06 12:36:55 -04:00
cmd adding grpc interface to network state (#33) 2018-05-14 18:31:26 -06:00
configs keep 2018-04-06 12:36:55 -04:00
deployments keep 2018-04-06 12:36:55 -04:00
docs Add error handling section 2018-04-11 07:43:23 -05:00
examples adding grpc interface to network state (#33) 2018-05-14 18:31:26 -06:00
githooks keep 2018-04-06 12:36:55 -04:00
init keep 2018-04-06 12:36:55 -04:00
internal HTTP Ranger (#11) 2018-04-17 07:39:14 -06:00
logo wip on structure 2018-04-06 12:32:34 -04:00
netstate/routes adding grpc interface to network state (#33) 2018-05-14 18:31:26 -06:00
pkg adding grpc interface to network state (#33) 2018-05-14 18:31:26 -06:00
protos adding grpc interface to network state (#33) 2018-05-14 18:31:26 -06:00
scripts don't require shallow clones of old commits (#38) 2018-05-09 16:21:53 +03:00
storage adding grpc interface to network state (#33) 2018-05-14 18:31:26 -06:00
test keep 2018-04-06 12:36:55 -04:00
third_party keep 2018-04-06 12:36:55 -04:00
tools keep 2018-04-06 12:36:55 -04:00
web keep 2018-04-06 12:36:55 -04:00
.gitignore Ignore VSCode settings and debug files (#41) 2018-05-10 12:23:26 -04:00
.travis.yml fix travis, and get a clean lint (#32) 2018-05-08 18:02:01 -04:00
go.mod go.mod fixes 2018-04-30 15:28:02 -04:00
Jenkinsfile echos for path 2018-04-26 09:04:15 -04:00
LICENSE.md wip on structure 2018-04-06 12:32:34 -04:00
Makefile don't require shallow clones of old commits (#38) 2018-05-09 16:21:53 +03:00
README.md update readme 2018-04-27 14:53:46 +02:00

Storj

Go Report Card Go Doc Release


Storj is a platform, token, and suite of decentralized applications that allows you to store data in a secure and decentralized manner. Your files are encrypted, shredded into little pieces called 'shards' and stored in a global decentralized network of computers. Only you have access and the ability to retrieve all shards from the network, decrypt them, and finally re-combine all file pieces into your original file.


To start using Storj

See our documentation at Storj docs.

To start developing Storj

The community site hosts all information about building storj from source, how to contribute code and documentation, who to contact about what, etc.

Install VGO

go get -u golang.org/x/vgo

Install non-go development dependencies

In order to develop on Storj, you will need to have the protobuf compiler installed on your system.

  1. Grab the latest release for your system from here.

  2. place the protoc binary in your path. i.e.

    mv $HOME/Downloads/protoc-<version>-<arch>/bin/protoc /usr/local/bin
    

Install go dependencies

Use vgo to install both dev and non-dev dependencies.

  1. Install development dependencies

    make build-dev-deps
    
  2. Install project dependencies

    # in project root
    vgo install
    

If you want to build Storj right away there are two options:

You have a working Go environment.
$ go get -d storj.io/storj
$ cd $GOPATH/src/storj.io/storj
$ make
You have a working Docker environment.
$ git clone https://github.com/storj/storj
$ cd storj
$ make docker

For the full story, head over to the [developer's documentation].

Support

If you need support, start with the [troubleshooting guide], and work your way through the process that we've outlined.

That said, if you have any questions or suggestions please reach out to us on rocketchat or twitter.