f338aa62ba
* chore: bump serde from 1.0.143 to 1.0.144 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.143 to 1.0.144. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.143...v1.0.144) --- updated-dependencies: - dependency-name: serde dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> * [auto-commit] Update all Cargo lock files Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: dependabot-buildkite <dependabot-buildkite@noreply.solana.com> |
||
|---|---|---|
| .. | ||
| build-proto | ||
| proto | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
| init-bigtable.sh | ||
README.md
BigTable Setup
Development Environment
The Cloud BigTable emulator can be used during development/test. See https://cloud.google.com/bigtable/docs/emulator for general setup information.
Process:
- Run
gcloud beta emulators bigtable startin the background - Run
$(gcloud beta emulators bigtable env-init)to establish theBIGTABLE_EMULATOR_HOSTenvironment variable - Run
./init-bigtable.shto configure the emulator - Develop/test
Production Environment
Export a standard GOOGLE_APPLICATION_CREDENTIALS environment variable to your
service account credentials. The project should contain a BigTable instance
called solana-ledger that has been initialized by running the ./init-bigtable.sh script.
Depending on what operation mode is required, either the
https://www.googleapis.com/auth/bigtable.data or
https://www.googleapis.com/auth/bigtable.data.readonly OAuth scope will be
requested using the provided credentials.
Forward proxy
Export BIGTABLE_PROXY environment variable for the forward proxy as you would
for HTTP_PROXY. This will establish a tunnel through the forward proxy for
gRPC traffic (the tunneled traffic will still use TLS as normal).