solana/storage-bigtable
mergify[bot] c70d9d3f31
v2.0: link openssl statically for Windows (backport of #3118) (#3156)
link openssl statically for Windows (#3118)

* ci: fix windows pipeline

* vendor openssl for windows

* add comment for the workaround

(cherry picked from commit 49d2298762)

Co-authored-by: Yihau Chen <yihau.chen@icloud.com>
2024-10-15 13:15:34 +08:00
..
build-proto chore: workspace inheritance (#29893) 2023-02-23 22:01:54 +08:00
proto chore: remove unused clippy attributes, derive_partial_eq_without_eq (#1516) 2024-05-29 12:36:30 +00:00
src Add num_partitions to Blockstore rewards (#1601) 2024-06-17 16:42:33 -06:00
Cargo.toml v2.0: link openssl statically for Windows (backport of #3118) (#3156) 2024-10-15 13:15:34 +08:00
README.md bigtable: allow forward proxy in gRPC connection (#25918) 2022-06-23 10:51:31 -06:00
init-bigtable.sh storage-bigtable: Upload entries (#34099) 2023-11-28 11:47:22 -07:00

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:

  1. Run gcloud beta emulators bigtable start in the background
  2. Run $(gcloud beta emulators bigtable env-init) to establish the BIGTABLE_EMULATOR_HOST environment variable
  3. Run ./init-bigtable.sh to configure the emulator
  4. 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).