gaspersic/solana
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Files
v1.7.13
solana/storage-bigtable
History
mergify[bot] 55f27d5c26 Fix memo handling and "blocks" key formatting (#20044) (#20080) 
* Fix memo handling and "blocks" key formatting

* Skip memo equality check

* Define slot_to_tx_by_addr_key

Co-authored-by: Justin Starry <justin@solana.com>
(cherry picked from commit 795dde109c)

Co-authored-by: Ryo Onodera <ryoqun@gmail.com>
2021-09-21 22:22:55 +00:00
..
build-proto
Bump 1.7 version (#19943)
2021-09-16 13:16:09 -06:00
proto
Bump prost, prost-types, and tonic (backport #18537) (#18558)
2021-07-09 19:54:29 +00:00
src
Fix memo handling and "blocks" key formatting (#20044) (#20080)
2021-09-21 22:22:55 +00:00
Cargo.toml
Bump 1.7 version (#19943)
2021-09-16 13:16:09 -06:00
init-bigtable.sh
Add configuration info
2020-08-05 14:27:12 -07:00
README.md
Add configuration info
2020-08-05 14:27:12 -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.