Go to file
Ethan cfca021839 satellite/accounting: Add chore to cleanup old project bandwidth rollups data
Removes old project_bandwidth_rollups records that are no longer used.

Uses a retain months configuration to determine how many months to save.  Current month cannot be removed.
Tests retainMonths=-1, 0, 2

Change-Id: Ia4be2546cdb28802427acf41ecd85ad66df3e62c
2020-07-22 18:56:49 +00:00
.github pr template: migrations run concurrently with api servers now 2019-10-31 09:27:46 -06:00
certificate all: fix dots 2020-07-16 14:58:28 +00:00
cmd cmd/storagenode,storage/cockroachkv: better error handling 2020-07-16 20:03:50 +03:00
docs Update automatic updater blueprint to catch missing requirement 2020-06-05 16:24:23 -06:00
examples all: fix dots 2020-07-16 14:58:28 +00:00
installer/windows storagenode/windows-installer: ignore set firewall exception error 2020-05-27 17:56:49 +03:00
pkg all: fix dots 2020-07-16 14:58:28 +00:00
private satellite/accounting: Add chore to cleanup old project bandwidth rollups data 2020-07-22 18:56:49 +00:00
resources Add LE CA to satellite and storagenode images (#1688) 2019-04-08 13:06:01 -04:00
satellite satellite/accounting: Add chore to cleanup old project bandwidth rollups data 2020-07-22 18:56:49 +00:00
scripts satellite/accounting: Add chore to cleanup old project bandwidth rollups data 2020-07-22 18:56:49 +00:00
storage cmd/storagenode,storage/cockroachkv: better error handling 2020-07-16 20:03:50 +03:00
storagenode storagenode/{monitor,piecestore}: if free disk < expected available space, return free disk 2020-07-22 15:08:37 +00:00
versioncontrol all: replace == comparison with errors.Is 2020-07-14 15:50:25 +00:00
web web/satellite: completed transaction state condition changed 2020-07-17 17:29:14 +03:00
.clabot clabot: change JTs username (#3917) 2020-07-03 21:19:58 +02:00
.dockerignore Forward-port release-alpha8 build script issues (#1726) 2019-04-09 23:01:10 -06:00
.gitignore cmd/gateway: remove gateway command from repository and adjust `make 2020-03-27 07:42:42 +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/metainfo: restore tests disabled to remove StreamID from 2020-07-22 13:54:39 +00:00
go.sum satellite/metainfo: restore tests disabled to remove StreamID from 2020-07-22 13:54:39 +00:00
Jenkinsfile ci: update to Go 1.14.6 2020-07-20 13:17:49 +00:00
Jenkinsfile.public tests: allow STORJ_TEST_POSTGRES 2020-07-10 16:43:49 +03:00
LICENSE license code with agplv3 (#126) 2018-07-05 10:24:26 -04:00
Makefile ci: update to Go 1.14.6 2020-07-20 13:17:49 +00:00
monkit.lock satellite/satellitedb: Monitor node tallies 2020-07-17 10:21:42 -06:00
package-lock.json Satellite api keys frontend (#1039) 2019-02-01 18:19:30 +02:00
README.md updating Aha link on our readme 2020-05-04 14:21:58 -04: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.