2a59679766
* separate TLS options from server options (because we need them for dialing too) * stop creating transports in multiple places * ensure that we actually check revocation, whitelists, certificate signing, etc, for all connections. |
||
|---|---|---|
| .. | ||
| main.go | ||
| README.md | ||
gRPC Client + BoltDB Crud Interface
This is an example gRPC client which makes CRUD requests (create, read, update, delete) for storing pointers at given paths in BoltDB.
The gRPC server at storj.io/storj/cmd/pointerdb/main.go needs to be running for this to work.
To run the client:
go run examples/pointerdb-client/main.go
You can change the port number with a flag if necessary: -port=<port-number>
Afterward, you can use Bolter or a similar BoltDB viewer to make sure your pointer entries were changed as expected.
If changes are made to storj.io/storj/pkg/pb/pointerdb.proto, the protobuf file will need to be regenerated by running go generate inside pkg/pb.
Tests for this example code can be found in storj.io/storj/pkg/pointerdb/client_test.go.