Go to file
Egon Elbre bbf81f2479 Consolidate identity management to identity cli commands (#1083)
* Consolidate identity management:

Move identity cretaion/signing out of storagenode setup command.

* fixes

* linters

* Consolidate identity management:

Move identity cretaion/signing out of storagenode setup command.

* fixes

* sava backups before saving signed certs

* add "-prebuilt-test-cmds" test flag

* linters

* prepare cli tests for travis

* linter fixes

* more fixes

* linter gods

* sp/sdk/sim

* remove ca.difficulty

* remove unused difficulty

* return setup to its rightful place

* wip travis

* Revert "wip travis"

This reverts commit 56834849dcf066d3cc0a4f139033fc3f6d7188ca.

* typo in travis.yaml

* remove tests

* remove more

* make it only create one identity at a time for consistency

* add config-dir for consitency

* add identity creation to storj-sim

* add flags

* simplify

* fix nolint and compile

* prevent overwrite and pass difficulty, concurrency, and parent creds

* goimports
2019-01-18 11:36:58 +01:00
cmd Consolidate identity management to identity cli commands (#1083) 2019-01-18 11:36:58 +01:00
examples storagenode dashboard is working and passing tests locally (#1072) 2019-01-16 16:09:13 -05:00
internal Consolidate identity management to identity cli commands (#1083) 2019-01-18 11:36:58 +01:00
pkg Consolidate identity management to identity cli commands (#1083) 2019-01-18 11:36:58 +01:00
resources give our appearence on windows some love (#429) 2018-10-16 14:48:17 -04:00
satellite Generate Payments Report (#1079) 2019-01-17 13:34:13 -05:00
scripts Remove captplanet (#1070) 2019-01-17 04:35:22 -05:00
storage storelogger: truncate value output (#995) 2019-01-09 13:18:23 +02:00
storagenode convert piecestorage into a struct (#1024) 2019-01-11 13:26:39 +02:00
test Build and upload binaries (#296) 2018-08-31 11:21:44 -04:00
web/satellite minor web satelite ui bug fixes (#1031) 2019-01-14 17:39:21 +02:00
.clabot Update .clabot (#810) 2018-12-10 08:43:25 -05:00
.dockerignore Test all-in-one (#900) 2019-01-03 14:54:27 -05:00
.gitignore Disconnects nodeclient, routing table dbs when done with kademlia (#507) 2018-10-26 10:07:02 -04:00
.golangci.yml Separate storj.io packages in imports (#481) 2018-10-16 14:43:44 +03:00
.travis.yml Consolidate identity management to identity cli commands (#1083) 2019-01-18 11:36:58 +01:00
all-in-one.md Attempt at fixing the all-in-one environment (#736) 2018-12-04 16:10:23 -05:00
CODE_OF_CONDUCT.md Adding CODE_OF_CONDUCT to storj/storj repo (#779) 2018-12-07 15:10:02 -05:00
docker-compose.yaml Reduce test CA difficulty (#1010) 2019-01-10 15:23:33 +01:00
go.mod storagenode dashboard is working and passing tests locally (#1072) 2019-01-16 16:09:13 -05:00
go.sum cmd/bootstrap: a kademlia-only server (#1001) 2019-01-09 17:59:51 +02:00
Jenkinsfile Limit Jenkins to only one build at a time (#893) 2018-12-17 15:33:59 -05:00
LICENSE license code with agplv3 (#126) 2018-07-05 10:24:26 -04:00
Makefile Consolidate identity management to identity cli commands (#1083) 2019-01-18 11:36:58 +01:00
README.md Update README.md 2018-12-29 19:02:55 -07:00

Storj V3 Network

Go Report Card Go Doc Coverage Status Alpha

Storj is building a decentralized cloud storage network. Check out our white paper for more info!


Storj is an S3-compatible platform and suite of decentralized applications that allows you to store data in a secure and decentralized manner. Your files are encrypted, broken into little pieces and stored in a global decentralized network of computers. Luckily, we also support allowing you (and only you) to retrieve those files!

Table of Contents

Contributing to Storj

All of our code for Storj v3 is open source. Have a code change you think would make Storj better? Please send a pull request along! Make sure to sign our Contributor License Agreement (CLA) first. See our license section for more details.

Have comments, bug reports, or suggestions? Want to propose a PR before hand-crafting it? Jump on to our Rocketchat and join the #dev channel to say hi to the developer community and to talk to the Storj core team.

Issue tracking and roadmap

See the breakdown of what we're building by checking out the following resources:

Install required packages

To get started running Storj locally, download and install the latest release of Go (at least Go 1.11) at golang.org.

You will also need Git. (brew install git, apt-get install git, etc). If you're building on Windows, you also need to install and have gcc setup correctly.

We support Linux, Mac, and Windows operating systems. Other operating systems supported by Go should also be able to run Storj.

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.

First, fork our repo and clone your copy of our repository.

git clone git@github.com:<your-username>/storj storj
cd storj

Then, let's install Storj.

go install -v ./cmd/...

Make changes and test

Make the changes you want to see! Once you're done, you can run all of the unit tests:

go test -v ./...

You can also 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.

Push up a pull request

Use Git to push your changes to your fork:

git commit -a -m 'my changes!'
git push origin master

Use Github to open a pull request!

Start using Storj

Our wiki has documentation and tutorials. Check out these three tutorials:

License

The network under construction (this repo) is currently licensed with the AGPLv3 license. Once the network reaches beta phase, we will be licensing all client-side code via the Apache v2 license.

For code released under the AGPLv3, we request that contributors sign our Contributor License Agreement (CLA) so that we can relicense the code under Apache v2, or other licenses in the future.

Support

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