Go to file
Jeff Wendling 140251882e
fix bug for setting flag only values in process setup (#2089)
* fix bug for setting flag only values in process setup

when the code was changed to directly load values into the config
structs, it was missed that some configuration is only defined
through flags, but can be loaded from config files still.

so, we need to propogate the settings to the flag only values.

* add test for setting propagation

* fix linting error
2019-05-31 21:15:50 +00:00
.github storagenode: delete psserver (#1837) 2019-04-26 08:17:18 +03:00
bootstrap Enable gocritic linter (#2051) 2019-05-29 09:14:25 -04:00
cmd Command line flags features and cleanup (#2068) 2019-05-29 17:56:22 +00:00
docs/design Value Attribution design doc (#1996) 2019-05-30 10:12:34 -04:00
examples pkg/cfgstruct: tie defaults to releases (#1787) 2019-04-19 12:17:30 -06:00
internal Satellite voucher service (#2043) 2019-05-30 15:52:33 -04:00
lib/uplink Java/Android libuplink bindings (#1918) 2019-05-24 10:13:01 +02:00
mobile Java/Android libuplink bindings (#1918) 2019-05-24 10:13:01 +02:00
pkg fix bug for setting flag only values in process setup (#2089) 2019-05-31 21:15:50 +00:00
resources Add LE CA to satellite and storagenode images (#1688) 2019-04-08 13:06:01 -04:00
satellite add disqualified column to nodes table (#2086) 2019-05-30 17:38:23 -04:00
scripts Make maxReverifyCount configurable (#2071) 2019-05-31 17:23:00 +02:00
storage Enable Scopelint Linter (#2049) 2019-05-29 09:30:16 -04:00
storagenode Add monkit stats to piecestore upload/download (#2078) 2019-05-30 11:44:47 -04:00
uplink Enable gocritic linter (#2051) 2019-05-29 09:14:25 -04:00
versioncontrol Add Identity to Version Control Server (#1876) 2019-05-01 18:21:51 +02:00
web add payment popup added (#2032) 2019-05-29 19:22:16 +03:00
.clabot Add ReneSmeekes (#2057) 2019-05-25 18:01:16 +02:00
.dockerignore Forward-port release-alpha8 build script issues (#1726) 2019-04-09 23:01:10 -06:00
.gitignore Disconnects nodeclient, routing table dbs when done with kademlia (#507) 2018-10-26 10:07:02 -04:00
.golangci.yml Enable Scopelint Linter (#2049) 2019-05-29 09:30:16 -04: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 testplanet.Run (#1222) 2019-02-04 22:37:46 +02:00
Dockerfile.jenkins cover all the things (#1818) 2019-04-26 16:39:11 +03:00
go.mod Command line flags features and cleanup (#2068) 2019-05-29 17:56:22 +00:00
go.sum Command line flags features and cleanup (#2068) 2019-05-29 17:56:22 +00:00
Jenkinsfile Fix Jenkins master builds (#1889) 2019-05-03 14:14:38 -04:00
Jenkinsfile.public add postgres support to storj-sim (#1908) 2019-05-14 08:13:18 -07:00
LICENSE license code with agplv3 (#126) 2018-07-05 10:24:26 -04:00
Makefile I think this fixes the weird '-heads-' in the version tags (#2010) 2019-05-21 16:36:08 +02:00
package-lock.json Satellite api keys frontend (#1039) 2019-02-01 18:19:30 +02:00
proto.lock filter duplicate node IPs (#1890) 2019-05-22 16:06:27 -04:00
README.md Direct suggestions to ideas.storj.io (#1891) 2019-05-07 22:14:25 +02: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 or bug reports? 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.

Want to vote on or suggest new features? Post it on ideas.storj.io.

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 email us at support@tardigrade.io.