2e34b631b1
Allow the satellite commands which uses the live accounting cache (core and API) to run when at the time that its instantiated there is an error connecting to the backend. This prevent that if live accounting backend is down we can run these services because: 1. The services must run despite of the cache backend being down although it may be degraded. 2. We may need to start new replicas of the services or the services in a different place while we are troubleshooting and fixing the cache backend system. 3. Our services may restart when the cache backend or the network connecting to it fails momentarily. Change-Id: Ic93f9571bc0865c9488d64ab1356376fae797efc |
||
|---|---|---|
| .. | ||
| reports | ||
| admin.go | ||
| api.go | ||
| billing.go | ||
| compensation.go | ||
| Dockerfile | ||
| entrypoint | ||
| 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