48da8baab5
for storj-sim to work, we need to avoid schemas in cockroach urls so we have storj-sim create namespaced databases instead of schemas and we have the migrate command create the database in the same way that it would create a schema for postgres. then it works! a follow up commit will move the creation of the database/schemas into storj-sim's setup step so that we can avoid doing these icky creations during normal migration calls. it will also make the pointerdb have an explicit call to migrate instead of just doing it every time it's opened. Change-Id: If69ef5cb96b6866b0438c761bd445afb3597ae5f |
||
|---|---|---|
| .. | ||
| reports | ||
| api.go | ||
| Dockerfile | ||
| entrypoint | ||
| gracefulexit.go | ||
| main.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