Go to file
Jess G d51bdf14df
project usage limiting (#1561)
* reorg uplink cmd files for consistency

* init implementation of usage limiting

* Revert "reorg uplink cmd files for consistency"

This reverts commit 91ced7639bf36fc8af1db237b01e233ca92f1890.

* add changes per CR comments

* fix custom query to use rebind

* updates per convo about what to limit on

* changes per comments

* fix syntax and comments

* add integration test, add db methods for test

* update migration, add rebind to query

* update testdata for psql

* remove unneeded drop index statement

* fix migrations, fix calculate usage limit

* fix comment

* add audit test back

* change methods to use bucketName/projectID, fix tests

* add changes per CR comments

* add test for uplink upload and err ssg

* changes per CR comments

* check get/put limit separately
2019-04-02 11:21:18 -07:00
.github clarify who fills in the code review checklist (#1555) 2019-03-27 17:19:22 -06:00
bootstrap remove utils.CombineErrors and utils.ErrorGroup (#1603) 2019-03-29 14:30:23 +02:00
cmd API endpoint checking object and segment health from the satellite (#1546) 2019-04-02 10:55:58 -04:00
examples Remove PointerDB client (#1520) 2019-03-22 11:01:49 +02:00
internal project usage limiting (#1561) 2019-04-02 11:21:18 -07:00
lib/uplink remove utils.CombineErrors and utils.ErrorGroup (#1603) 2019-03-29 14:30:23 +02:00
pkg project usage limiting (#1561) 2019-04-02 11:21:18 -07:00
resources give our appearence on windows some love (#429) 2018-10-16 14:48:17 -04:00
satellite project usage limiting (#1561) 2019-04-02 11:21:18 -07:00
scripts make tests run faster (#1553) 2019-03-22 15:14:17 +02:00
storage storagenode/pieces: ensure we can call Commit or Cancel only once (#1511) 2019-03-18 16:29:54 +02:00
storagenode migration tests for storagenodedb infodb (#1628) 2019-04-02 09:54:09 +02:00
uplink devDefaults for easy uplink setup connecting to storj-sim (#1583) 2019-03-27 09:16:37 +02:00
web Web forgot password flow markup (#1627) 2019-04-02 16:38:57 +03:00
.clabot Add Fadila to CLA list (#1623) 2019-04-01 12:33:37 +02: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 Don't change linter concurrency (#1112) 2019-01-23 13:21:56 +02:00
.travis.yml make tests run faster (#1553) 2019-03-22 15:14:17 +02: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
go.mod API endpoint checking object and segment health from the satellite (#1546) 2019-04-02 10:55:58 -04:00
go.sum API endpoint checking object and segment health from the satellite (#1546) 2019-04-02 10:55:58 -04: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 Fix image tags (#1541) 2019-03-21 07:48:39 -04:00
package-lock.json Satellite api keys frontend (#1039) 2019-02-01 18:19:30 +02:00
proto.lock Remove pointerdb.Server (#1609) 2019-03-30 13:21:49 +02:00
README.md Added Travis CI build status icon. (#1636) 2019-04-02 10:34:31 -04:00

Storj V3 Network

Go Report Card Go Doc Coverage Status Alpha Build Status

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.