d4ad3a3ca6
Before, the VA query was summing the total and dividing by the number of rows. This gives the average bytes stored per hour, but we charge for usage with byte-hours. Why not do value attribution the same way? To do that, we don't divide by the number of rows. We also have object and segment fees so return segment-hours and object-hours too. Change-Id: I1f18b7e1b2bae1d3fae1ca3b93bfc24db5b9b0e6 |
||
|---|---|---|
| .. | ||
| reports | ||
| admin.go | ||
| api.go | ||
| billing.go | ||
| compensation.go | ||
| Dockerfile | ||
| entrypoint | ||
| fetchpieces.go | ||
| gc.go | ||
| gracefulexit.go | ||
| main.go | ||
| output.go | ||
| README.md | ||
| repairer.go | ||
| satellite.yaml | ||
| usage.go | ||
Satellite
Documentation for developing and building the satellite service
Usage:
First make an identity:
go install storj.io/storj/cmd/satellite
satellite setup
You can edit ~/.storj/satellite/config.yaml to your liking. Then run it!
satellite run