History

Andrew Harding 62c58f4a9a satellite: consistent report range arguments This change updates the three satellite report commands that accept date ranges to parse and treat those dates uniformly. - End dates are now uniformly exclusive. Exclusive end dates helps operators avoid one-off errors on month boundaries, as in the operator does not have to remember how many days are in that month and can just run the report from the 1st (inclusive) through the 1st (exclusive). - Fixed the date range validity check which only failed if the start date came after the end date (it should have failed dates that were equal since the check happened after adjusting for inclusivity). Change-Id: Ib2ee1c71ddb916c6e1906834d5ff0dc47d1a5801		2019-12-20 17:17:09 +00:00
..
reports	satellite: consistent report range arguments	2019-12-20 17:17:09 +00:00
api.go	private: rename internal to private (#3573 )	2019-11-14 21:46:15 +02:00
Dockerfile	storagenode/dashboard: Enable storagenode dashboard in docker images (#3024 )	2019-09-16 15:09:59 +02:00
entrypoint	satellitedb: separate migration into subcommand (#3436 )	2019-11-02 13:09:07 -07:00
gracefulexit.go	satellite/gracefulexit: Add graceful exit completed/failed receipt verification to satellite CLI (#3679 )	2019-12-03 17:09:39 -05:00
main.go	satellite: consistent report range arguments	2019-12-20 17:17:09 +00:00
README.md	hc to satellite rename (#282 )	2018-08-29 14:32:41 -04:00
repairer.go	private: rename internal to private (#3573 )	2019-11-14 21:46:15 +02:00
satellite.yaml	hc to satellite rename (#282 )	2018-08-29 14:32:41 -04:00
usage.go	cmd/satellite: add graceful exit reports command to satellite CLI (#3300 )	2019-10-22 21:06:01 -04:00

README.md

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