Go to file
Moby von Briesen e115bc1903 cmd/storagenode;storagenode/storagenodedb: add preflight database check
for storagenode

Ensure that database schema matches latest test migration schema before
allowing the node to start up.

Ensure minimal read/write functionality for each storagenode database
before allowing the node to start up.

This will eliminate many unhandled audit errors we are seeing.

Change-Id: Ic0e628b04a9c35b7a8243f6a81d4683918170ba9
2020-01-16 18:44:46 +00:00
.github pr template: migrations run concurrently with api servers now 2019-10-31 09:27:46 -06:00
certificate common: separate repository 2019-12-27 14:11:15 +02:00
cmd cmd/storagenode;storagenode/storagenodedb: add preflight database check 2020-01-16 18:44:46 +00:00
docs storagenode/trust: wire up list into pool 2019-12-13 20:32:50 +00:00
examples uplink: move to storj.io/uplink (#3746) 2020-01-08 15:40:19 +02:00
installer/windows installer/windows: batch file improvements (#3441) 2020-01-03 15:28:04 +02:00
lib cmd: rename "scope" flag to "access" 2020-01-10 15:27:53 +00:00
linksharing cmd: rename "scope" flag to "access" 2020-01-10 15:27:53 +00:00
pkg satellitedb: save out all db-touching traces 2020-01-14 18:47:45 -05:00
private satellite/accounting: refactor live accounting to hold current estimated totals 2020-01-16 10:26:49 -05:00
resources Add LE CA to satellite and storagenode images (#1688) 2019-04-08 13:06:01 -04:00
satellite satellite/accounting: refactor live accounting to hold current estimated totals 2020-01-16 10:26:49 -05:00
scripts scripts/testversions,rollingupgrade: remove encrytion key 2020-01-16 16:01:34 +00:00
storage satellite/accounting: refactor live accounting to hold current estimated totals 2020-01-16 10:26:49 -05:00
storagenode cmd/storagenode;storagenode/storagenodedb: add preflight database check 2020-01-16 18:44:46 +00:00
versioncontrol common: separate repository 2019-12-27 14:11:15 +02:00
web web/satellite: forgot password error message removed 2020-01-15 16:24:38 +00:00
.clabot adding Igor Gaidaenko our new team member! (#3726) 2019-12-11 13:54:12 -05:00
.dockerignore Forward-port release-alpha8 build script issues (#1726) 2019-04-09 23:01:10 -06:00
.gitignore mobile: build libuplink aar (#3165) 2019-10-04 01:56:42 -07:00
.golangci.yml jenkins: update to golangci-lint 1.21.0 (#3289) 2019-10-17 10:42:22 +03: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 satellitedb: save out all db-touching traces 2020-01-14 18:47:45 -05:00
go.sum Revert "dbutil: statically require all databases accesses to use contexts" 2020-01-15 07:28:00 +00:00
Jenkinsfile jenkins: bump go to 1.13.6 2020-01-13 13:57:56 -05:00
Jenkinsfile.public uplink: move to storj.io/uplink (#3746) 2020-01-08 15:40:19 +02:00
LICENSE license code with agplv3 (#126) 2018-07-05 10:24:26 -04:00
Makefile jenkins: bump go to 1.13.6 2020-01-13 13:57:56 -05:00
monkit.lock uplink: move to storj.io/uplink (#3746) 2020-01-08 15:40:19 +02: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.