Go to file
JT Olio 5511827662 satellite/orders: don't log expired order limits
we still need to come up with a better plan to get storage nodes
to stop doing this, but in the meantime, we know this is happening,
just stop logging it and keep some stats instead.

Change-Id: Icb6bcba275e0e955c54b1a90da2b37219fff2349
2020-03-26 22:31:10 -06:00
.github pr template: migrations run concurrently with api servers now 2019-10-31 09:27:46 -06:00
certificate bump storj.io/common to latest 2020-03-25 09:08:40 -04:00
cmd bump storj.io/common to latest 2020-03-25 09:08:40 -04:00
docs docs/blueprints: Add design doc for distributed tracing. 2020-02-25 20:29:05 +00:00
examples storj: remove from storj/pkg packages moved to storj/private repo 2020-03-24 09:56:29 +01:00
installer/windows removes bandwidth limiting 2020-03-04 14:04:00 +00:00
lib libuplink: return deleted bucket/object (step 4) 2020-03-19 13:32:07 +02:00
pkg pkg/server: add counters for grpc calls 2020-03-25 21:38:13 +02:00
private satellite/gc: update release default for gc to run separately (#3830) 2020-03-26 14:44:18 -04:00
resources Add LE CA to satellite and storagenode images (#1688) 2019-04-08 13:06:01 -04:00
satellite satellite/orders: don't log expired order limits 2020-03-26 22:31:10 -06:00
scripts satellite/gc: update release default for gc to run separately (#3830) 2020-03-26 14:44:18 -04:00
storage private/dbutil: add database name to configure as a tag 2020-03-26 16:50:15 +00:00
storagenode private/dbutil: add database name to configure as a tag 2020-03-26 16:50:15 +00:00
versioncontrol storj: remove storj/private/version package which was moved to 2020-03-24 14:31:33 +00:00
web satellite/console: email used error handling for registration 2020-03-26 17:42:33 +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
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 bump uplink version to latest 2020-03-26 09:03:53 +00:00
go.sum bump uplink version to latest 2020-03-26 09:03:53 +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 linksharing: move to storj.io/linksharing 2020-03-19 16:49:00 +00:00
monkit.lock satellite/repair: add monitoring for remote_segments_healthy_percentage 2020-03-17 17:45:59 +00:00
package-lock.json Satellite api keys frontend (#1039) 2019-02-01 18:19:30 +02:00
README.md Update README.md (#3828) 2020-03-25 19:53:11 -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 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!

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.