Go to file
Jeff Wendling a65aecfd98 compensation: always generate invoices for every node
instead of only generating invoices for nodes that had some
activity, we generate it for every node so that we can find
and pay terminal nodes that did not meet thresholds before
we recognized them as terminal.

Change-Id: Ibb3433e1b35f1ddcfbe292c034238c9fa1b66c44
2021-03-29 14:15:45 +00:00
.github all: switch from master to main 2020-12-28 22:59:06 +01:00
certificate certificate: move protobuf to storj/storj repository 2021-03-29 12:59:49 +00:00
cmd compensation: always generate invoices for every node 2021-03-29 14:15:45 +00:00
docs blueprint: layer2 support for zksync 2021-03-01 23:41:11 +00:00
installer/windows storagenode/windows-installer: ignore set firewall exception error 2020-05-27 17:56:49 +03:00
multinode multinode/multinodedb: add sqlite3 support 2021-02-11 16:36:05 +00:00
pkg redis: Rename functions prefixed with New by Open 2021-03-25 06:09:27 +00:00
private satellite/overlay: remove Inspector 2021-03-29 12:26:10 +03:00
resources cmd: add ca-certificates to Docker images (#3986) 2020-12-08 01:38:33 +01:00
satellite compensation: always generate invoices for every node 2021-03-29 14:15:45 +00:00
scripts tests: fix calculation of previous month for billing integration test 2021-03-29 10:38:59 +02:00
storage redis: Rename functions prefixed with New by Open 2021-03-25 06:09:27 +00:00
storagenode pb: use *UnimplementedServer to avoid breaking API changes 2021-03-29 12:26:10 +03:00
versioncontrol versioncontrol: add process url resolver 2021-01-15 17:11:08 +00:00
web satellite/wasm: support restricting full access grants to paths 2021-03-26 19:49:21 +00:00
.dockerignore Forward-port release-alpha8 build script issues (#1726) 2019-04-09 23:01:10 -06:00
.gitignore satellite/console/wasm: reduce size to <9MB 2020-12-14 16:41:39 +00: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 satellite/testing: Change testing to use PG 12.3 (#3913) 2020-06-25 20:17:39 +03:00
go.mod satellite: update tests to pass etag.Reader to multipart.PutObjectPart 2021-03-29 13:18:11 +00:00
go.sum satellite: update tests to pass etag.Reader to multipart.PutObjectPart 2021-03-29 13:18:11 +00:00
Jenkinsfile rollingupgrade: add migration to metabase 2021-03-25 10:52:35 +00:00
Jenkinsfile.public certificate: move protobuf to storj/storj repository 2021-03-29 12:59:49 +00:00
LICENSE license code with agplv3 (#126) 2018-07-05 10:24:26 -04:00
Makefile certificate: move protobuf to storj/storj repository 2021-03-29 12:59:49 +00:00
monkit.lock Merge remote-tracking branch 'origin/main' into multipart-upload 2021-02-02 19:19:04 +02:00
package-lock.json Satellite api keys frontend (#1039) 2019-02-01 18:19:30 +02:00
proto.lock certificate: move protobuf to storj/storj repository 2021-03-29 12:59:49 +00:00
README.md quick update to readme (#4033) 2021-01-28 10:16:57 -05: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 forum and join the Engineering Discussions 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 the forum.

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.13) 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/identity. 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 main

Use Github to open a pull request!

A Note about Versioning

While we are practicing semantic versioning for our client libraries such as uplink, we are not practicing semantic versioning in this repo, as we do not intend for it to be used via Go modules. We may have backwards-incompatible changes between minor and patch releases in this repo.

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