Go to file
JT Olio ae855fd6eb
Forward-port release-alpha8 build script issues (#1726)
* releases: update alpha dockerfiles to embed release tags

Change-Id: I2978d3ed77d1b768be24ec9194bc404cd92e4700

* release script use plain shell

Change-Id: Ie4ca6633014e3bf00ac0c82e28905174a6ade95b

* removed /scripts from .dockerignore

Change-Id: Ib555236d62fb3dc354689284ac4a032d5b4b3aa8

* switch back to bash

Change-Id: Ie0958cde71cd396f44ac28c177f48df0bea7ba22

* fix go1.12 modules

Change-Id: If4c8364e7271f09febd1a6c8bfc731d723d344d9

* make sure the work tree is clean

Change-Id: Ie6e52af28e2bc52880d92a3b574d1f859fc8e88e
2019-04-09 23:01:10 -06:00
.github adds what and why prompts to pr template (#1701) 2019-04-08 15:01:52 -04:00
bootstrap internal/version: do version checks much earlier in the process initialization, take 2 (#1666) 2019-04-04 17:40:07 +02:00
cmd Forward-port release-alpha8 build script issues (#1726) 2019-04-09 23:01:10 -06:00
examples Remove PointerDB client (#1520) 2019-03-22 11:01:49 +02:00
internal Identity versioning fix (#1721) 2019-04-09 13:01:45 -04:00
lib/uplink Identity versioning fix (#1721) 2019-04-09 13:01:45 -04:00
pkg disable datarepair test for now (#1727) 2019-04-09 22:31:55 -06:00
resources Add LE CA to satellite and storagenode images (#1688) 2019-04-08 13:06:01 -04:00
satellite V3-1399 Error messages (#1715) 2019-04-10 03:15:12 +03:00
scripts Forward-port release-alpha8 build script issues (#1726) 2019-04-09 23:01:10 -06:00
storage storagenode/pieces: ensure we can call Commit or Cancel only once (#1511) 2019-03-18 16:29:54 +02:00
storagenode upload, download and delete success message on log level info (#1704) 2019-04-09 01:14:09 +02:00
uplink Replace localhost with 127.0.0.1 in defaults (#1678) 2019-04-05 14:09:16 +02:00
versioncontrol Add Versioning Server (#1576) 2019-04-03 21:13:39 +02:00
web V3-1399 Error messages (#1715) 2019-04-10 03:15:12 +03:00
.clabot Adding Ivan to the CLA bot (#1693) 2019-04-08 11:15:17 -04:00
.dockerignore Forward-port release-alpha8 build script issues (#1726) 2019-04-09 23:01:10 -06: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 Use go 1.12.1 for compiling in Travis (#1695) 2019-04-08 10:47:01 -04: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 Console usage rollup api (#1664) 2019-04-04 17:56:20 +03:00
go.sum Console usage rollup api (#1664) 2019-04-04 17:56:20 +03: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 Build multiarch ARM32v6 and AMD64 images (#1686) 2019-04-08 16:01:20 -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.