Go to file
Dylan Lott f445fab28b
Config updates (#141)
* Updates to config handling

- Add functions to load in configs
- Standardize location and naming of config files
- Configuration over convention style of config file handling for each
service

* update config handling and correclty handle cli flags being set

* generate configs from default if no config is found

- renamed pointerdbDB to pointerdb for clarity in config file
- set sane default for pkg/overlay boltDB file
- set srvPort to default to 8082 to avoid port collision on default
setting

* linter updates

* move boltdb path vars into function

* update tests to handle config environment changes

* --fix exec test mocks

* update tests to use viper instead of flag library

* fix typo

* add redis-server to services in travis for tests

* update examples with new config env function signature

* fix tests
2018-07-18 18:09:38 -06:00
cmd Errcheck (#133) 2018-07-16 15:22:34 -04:00
docs Add error handling section 2018-04-11 07:43:23 -05:00
examples Config updates (#141) 2018-07-18 18:09:38 -06:00
internal Config updates (#141) 2018-07-18 18:09:38 -06:00
logo wip on structure 2018-04-06 12:32:34 -04:00
pkg Config updates (#141) 2018-07-18 18:09:38 -06:00
pointerdb/auth rename netstate to pointerdb (#127) 2018-07-06 15:43:53 -04:00
protos ObjectStore (#128) 2018-07-16 23:44:28 +03:00
scripts Automatically build, tag and push docker images on merge to master (#103) 2018-06-21 15:36:39 -04:00
static Cache (#67) 2018-06-05 17:06:37 -04:00
storage adds netstate pagination (#95) 2018-06-29 16:06:25 -04:00
.clabot adding Kiev team to CLA (#149) 2018-07-16 09:49:40 -04:00
.gitignore Admin node (#131) 2018-07-09 16:43:32 -06:00
.travis.yml Config updates (#141) 2018-07-18 18:09:38 -06:00
go.mod pkg/kademlia tests and restructuring (#97) 2018-06-22 09:33:57 -04:00
Gopkg.lock Admin node (#131) 2018-07-09 16:43:32 -06:00
Gopkg.toml dep init (#56) 2018-05-29 20:28:46 -06:00
index.html Cache (#67) 2018-06-05 17:06:37 -04:00
Jenkinsfile Fix jenkins (#139) 2018-07-13 11:02:33 -04:00
LICENSE license code with agplv3 (#126) 2018-07-05 10:24:26 -04:00
Makefile Errcheck (#133) 2018-07-16 15:22:34 -04:00
README.md adding coveralls / code coverage (#112) 2018-06-26 13:48:02 +02:00

Storj

Go Report Card Go Doc

Coverage Status


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.