storj/cmd/satellite
Egon Elbre f41d440944 all: reduce number of log messages
Remove starting up messages from peers. We expect all of them to start,
if they don't, then they should return an error why they don't start.
The only informative message is when a service is disabled.

When doing initial database setup then each migration step isn't
informative, hence print only a single line with the final version.

Also use shorter log scopes.

Change-Id: Ic8b61411df2eeae2a36d600a0c2fbc97a84a5b93
2020-01-06 19:03:46 +00:00
..
reports common: separate repository 2019-12-27 14:11:15 +02: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 common: separate repository 2019-12-27 14:11:15 +02:00
main.go all: reduce number of log messages 2020-01-06 19:03:46 +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

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