Go to file
Jennifer Johnson 1c1750e6be removes bandwidth limiting
On satellite, remove all references to free_bandwidth column in nodes table.
On storage node, remove references to AllocatedBandwidth and MinimumBandwidth and mark as deprecated.

Protobuf message, NodeCapacity, is left intact for backwards compatibility.
Once this is released to all satellites, we can drop the column from the DB.

Change-Id: I2ff6c6537fc9008a0c5588e951afea58ede85838
2020-03-04 14:04:00 +00:00
.github pr template: migrations run concurrently with api servers now 2019-10-31 09:27:46 -06:00
certificate all: use pbgrpc 2020-02-26 21:27:47 +02:00
cmd removes bandwidth limiting 2020-03-04 14:04:00 +00:00
docs docs/blueprints: Add design doc for distributed tracing. 2020-02-25 20:29:05 +00:00
examples private/grpctlsopts: grpc related tlsopts 2020-02-26 22:46:06 +02:00
installer/windows removes bandwidth limiting 2020-03-04 14:04:00 +00:00
lib cmd/gateway: simplify module handling 2020-02-26 17:59:45 +00:00
linksharing mod: bump common and uplink version 2020-02-12 14:33:54 +00:00
pkg pkg/server: use common implementation for user timeouts 2020-03-03 10:06:45 +00:00
private removes bandwidth limiting 2020-03-04 14:04:00 +00:00
resources Add LE CA to satellite and storagenode images (#1688) 2019-04-08 13:06:01 -04:00
satellite removes bandwidth limiting 2020-03-04 14:04:00 +00:00
scripts release/rollingupgrade: on release tags run rolling upgrade against previous release (#3792) 2020-03-03 23:56:32 +01:00
storage private/processgroup: moved to storj.io/common/processgroup 2020-03-03 10:50:33 +00:00
storagenode removes bandwidth limiting 2020-03-04 14:04:00 +00:00
versioncontrol common: separate repository 2019-12-27 14:11:15 +02:00
web web/storagenode: on logo click action added 2020-02-27 10:02:01 +00:00
.clabot Adding Monty Anderson to the CLA 2020-02-11 17:11:24 +00:00
.dockerignore Forward-port release-alpha8 build script issues (#1726) 2019-04-09 23:01:10 -06:00
.gitignore pkg/debug: separate debug endpoints to a server 2020-01-29 16:30:31 -05:00
.golangci.yml golangci: Enable new linter added to last release 2020-01-24 18:09:37 +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 Use Postgres 9.6 for Jenkins builds (#3729) 2019-12-13 10:03:06 -05:00
go.mod upgrade dependencies for trace db debug endpoint 2020-03-04 07:35:34 +00:00
go.sum upgrade dependencies for trace db debug endpoint 2020-03-04 07:35:34 +00:00
Jenkinsfile jenkins: Update Jenkins to use -e POSTGRES_HOST_AUTH_METHOD=trust when running postgres. 2020-02-19 00:22:04 +00:00
Jenkinsfile.public jenkins: disable npm audit as its failing everything 2020-02-10 13:32:40 -07:00
LICENSE license code with agplv3 (#126) 2018-07-05 10:24:26 -04:00
Makefile cmd/gateway: use proper module name 2020-02-26 21:44:40 +02:00
monkit.lock removes bandwidth limiting 2020-03-04 14:04:00 +00:00
package-lock.json Satellite api keys frontend (#1039) 2019-02-01 18:19:30 +02:00
README.md Update Coverage URL (#3737) 2019-12-30 21:21:24 +01: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 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.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 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 our community forum or email us at support@tardigrade.io.