miraland-storage-bigtable
| Crates.io | miraland-storage-bigtable |
| lib.rs | miraland-storage-bigtable |
| version | 1.19.2 |
| created_at | 2023-05-03 00:31:33.398388+00 |
| updated_at | 2024-11-08 06:08:30.835373+00 |
| description | Miraland Storage BigTable |
| homepage | https://solanalabs.com/ |
| repository | https://github.com/miraland-labs/miraland |
| max_upload_size | |
| id | 855032 |
| size | 330,210 |
Miraland (miralandlabs)
documentation
README
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 miraland-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).