b5ddfc6fa5
Backstory: I needed a better way to pass around information about the underlying driver and implementation to all the various db-using things in satellitedb (at least until some new "cockroach driver" support makes it to DBX). After hitting a few dead ends, I decided I wanted to have a type that could act like a *dbx.DB but which would also carry information about the implementation, etc. Then I could pass around that type to all the things in satellitedb that previously wanted *dbx.DB. But then I realized that *satellitedb.DB was, essentially, exactly that already. One thing that might have kept *satellitedb.DB from being directly usable was that embedding a *dbx.DB inside it would make a lot of dbx methods publicly available on a *satellitedb.DB instance that previously were nicely encapsulated and hidden. But after a quick look, I realized that _nothing_ outside of satellite/satellitedb even needs to use satellitedb.DB at all. It didn't even need to be exported, except for some trivially-replaceable code in migrate_postgres_test.go. And once I made it unexported, any concerns about exposing new methods on it were entirely moot. So I have here changed the exported *satellitedb.DB type into the unexported *satellitedb.satelliteDB type, and I have changed all the places here that wanted raw dbx.DB handles to use this new type instead. Now they can just take a gander at the implementation member on it and know all they need to know about the underlying database. This will make it possible for some other pending code here to differentiate between postgres and cockroach backends. Change-Id: I27af99f8ae23b50782333da5277b553b34634edc |
||
|---|---|---|
| .github | ||
| certificate | ||
| cmd | ||
| docs | ||
| examples | ||
| installer/windows | ||
| lib | ||
| linksharing | ||
| pkg | ||
| private | ||
| resources | ||
| satellite | ||
| scripts | ||
| storage | ||
| storagenode | ||
| uplink | ||
| versioncontrol | ||
| web | ||
| .clabot | ||
| .dockerignore | ||
| .gitignore | ||
| .golangci.yml | ||
| CODE_OF_CONDUCT.md | ||
| docker-compose.yaml | ||
| Dockerfile.jenkins | ||
| go.mod | ||
| go.sum | ||
| Jenkinsfile | ||
| Jenkinsfile.public | ||
| LICENSE | ||
| Makefile | ||
| monkit.lock | ||
| package-lock.json | ||
| proto.lock | ||
| README.md | ||
Storj V3 Network
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 GOPATHentirely, or setGO111MODULE=onbefore 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.