Go to file
Egon Elbre 23231a29b1
Reduce linter concurrency (#297)
Limit concurrency to reduce memory usage.
2018-08-28 18:00:18 +03:00
cmd Reduce linter concurrency (#297) 2018-08-28 18:00:18 +03:00
docs Add error handling section 2018-04-11 07:43:23 -05:00
examples Add functions for signing and verifying during bandwidth exchange (#246) 2018-08-27 14:35:27 -04:00
internal Enable more linters (#272) 2018-08-27 11:28:16 -06:00
logo wip on structure 2018-04-06 12:32:34 -04:00
pkg CA and identity commands (#235) 2018-08-28 00:23:48 +02:00
pointerdb/auth Refactor List in PointerDB (#163) 2018-07-27 09:02:59 +03:00
protos Streamstore impl of Stor interface (#191) 2018-08-23 21:56:38 -06:00
scripts All-in-one docker-compose project (#267) 2018-08-23 11:48:03 -04:00
static Cache (#67) 2018-06-05 17:06:37 -04:00
storage Enable more linters (#272) 2018-08-27 11:28:16 -06:00
test Add files for testing builds in docker (#161) 2018-07-25 17:47:02 -04:00
.clabot clabot: add egon (#259) 2018-08-21 12:23:28 -06:00
.gitignore cross-compilation: fix darwin (#293) 2018-08-27 15:06:55 -06:00
.travis.yml Test captplanet with travis (#226) 2018-08-14 12:58:16 -04:00
all-in-one.md All-in-one docker-compose project (#267) 2018-08-23 11:48:03 -04:00
CODE_OF_CONDUCT.md styling changes to the code of conduct (#234) 2018-08-16 10:07:30 -04:00
docker-compose.yaml All-in-one docker-compose project (#267) 2018-08-23 11:48:03 -04:00
go.mod cross-compilation: fix darwin (#293) 2018-08-27 15:06:55 -06:00
go.sum cross-compilation: fix darwin (#293) 2018-08-27 15:06:55 -06:00
Gopkg.lock cross-compilation: fix darwin (#293) 2018-08-27 15:06:55 -06:00
Gopkg.toml Fix the sha3 error with the build (#230) 2018-08-15 14:49:30 -04:00
index.html Cache (#67) 2018-06-05 17:06:37 -04:00
Jenkinsfile More fixes to the staging deploy process (#278) 2018-08-23 17:17:47 -04:00
LICENSE license code with agplv3 (#126) 2018-07-05 10:24:26 -04:00
Makefile Reduce linter concurrency (#297) 2018-08-28 18:00:18 +03:00
README.md go 1.11! woohoo! simplify readme (#288) 2018-08-26 10:38:38 -06:00

Storj V3 Network

Go Report Card Go Doc Coverage Status

Storj is in the midst of a rearchitecture. Please stay tuned for our v3 whitepaper!


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 and stored in a global decentralized network of computers. Luckily, we also support allowing you (and only you) to recover them!

Table of Contents

Start Using Storj

Download, setup, and run the latest release

Go here to download the latest build

  • TODO: add link when a build is released
  • TODO for how to run the release

Using Storj via the Storj CLI

Configure the Storj CLI

  1. In a new terminal setup the Storj CLI: $ storj setup
  2. Edit the API Key, overlay address, and pointer db address fields in the Storj CLI config file located at ~/.storj/cli/config.yaml with values from the captplanet config file located at ~/.storj/capt/config.yaml

Test out some Storj CLI commands!

  1. Create a bucket: $ storj mb s3://bucket-name
  2. Upload an object: $ storj cp ~/Desktop/your-large-file.mp4 s3://bucket-name
  3. List objects in a bucket: $ storj ls s3://bucket-name/
  4. Download an object: $ storj cp s3://bucket-name/your-large-file.mp4 ~/Desktop/your-large-file.mp4
  5. Delete an object: $ storj rm s3://bucket-name/your-large-file.mp4

Using Storj via the AWS S3 CLI

Configure AWS CLI

Download and install the AWS S3 CLI: https://docs.aws.amazon.com/cli/latest/userguide/installing.html

In a new terminal session configure the AWS S3 CLI:

$ aws configure
AWS Access Key ID [None]: insecure-dev-access-key
AWS Secret Access Key [None]: insecure-dev-secret-key
Default region name [None]: us-east-1
Default output format [None]:
$ aws configure set default.s3.multipart_threshold 1TB  # until we support multipart

Test out some AWS S3 CLI commands!

  1. Create a bucket: $ aws s3 --endpoint=http://localhost:7777/ mb s3://bucket-name
  2. Upload an object: $ aws s3 --endpoint=http://localhost:7777/ cp ~/Desktop/your-large-file.mp4 s3://bucket-name
  3. List objects in a bucket: $ aws s3 --endpoint=http://localhost:7777/ ls s3://bucket-name/
  4. Download an object: $ aws s3 --endpoint=http://localhost:7777/ cp s3://bucket-name/your-large-file.mp4 ~/Desktop/your-large-file.mp4
  5. Generate a URL for an object: $ aws s3 --endpoint=http://localhost:7777/ presign s3://bucket-name/your-large-file.mp4
  6. Delete an object: $ aws s3 --endpoint=http://localhost:7777/ rm s3://bucket-name/your-large-file.mp4

For more information about the AWS s3 CLI visit: https://docs.aws.amazon.com/cli/latest/reference/s3/index.html

Start Contributing to Storj

Install required packages

Download and install the latest release of Go, at least Go 1.11: https://golang.org/

You will also need Git. (brew install git, apt-get install git, etc).

Install git and golang. We support Linux, Mac, and Windows operating systems. Other operating systems supported by Go are probably not much additional work.

Download and compile Storj

Aside about GOPATH: Go 1.11 supports a new feature called Go modules, and Storj has adopted Go module support. If you've used previous Go versions, Go modules no longer require a GOPATH environment variable. Go by default falls back to the old behavior if you check out code inside of the directory referenced by your GOPATH variable, so make sure to use another directory, unset GOPATH entirely, or set GO111MODULE=on before continuing with these instructions. If you don't have a GOPATH set, you can ignore this aside.

git clone git@github.com:storj/storj storj
cd storj
go install -v ./cmd/...

Configure a test network

~/go/bin/captplanet setup

Start the test network

~/go/bin/captplanet run

Try out some commands via Storj CLI or AWS CLI

Run unit tests

go test -v ./...

You can execute only a single test package if you like. For example: go test ./pkg/kademlia. Add -v for more informations about the executed unit tests.

Support

If you have any questions or suggestions please reach out to us on Rocketchat or Twitter.