-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #70 from semiotic-ai/joseph/back-179-bring-example…
…s-to-fore-in-vee-crate-documentation docs: bring examples to fore in vee crate documentation
- Loading branch information
Showing
17 changed files
with
357 additions
and
261 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,26 @@ | ||
# Firehose Protos Examples | ||
|
||
Here's an example of how to run one of the examples in the `firehose-protos-examples` crate: | ||
Examples that use methods implemented on the Rust-compiled Firehose | ||
protobuffer types from [Firehose Protos](../firehose_protos/index.html). | ||
|
||
## Running Examples | ||
|
||
To run the examples, you need access to a Firehose provider for each chain from which you want | ||
to extract data - an endpoint and an API key (if the latter is required). | ||
|
||
If you need access to a Firehose provider, we suggest using [Pinax](https://app.pinax.network/). | ||
|
||
Add your endpoint and API key to a `.env` file in the root of the repository. See `.env.examples` for | ||
a configuration template. | ||
|
||
To run individual examples, use the following command: | ||
|
||
```terminal | ||
cd crates/firehose-protos-examples && cargo run -- --examples receipt_root | ||
cargo run -p firehose-protos-examples --example <example_name> | ||
``` | ||
|
||
Use environment variables to provide Firehose Ethereum and Firehose | ||
Beacon providers of your choice. | ||
So, for example, to run the `receipt_root` example: | ||
|
||
To do this, place a `.env` file in the root of `veemon`. See the | ||
`.env.example` file in the root of this repository for what you'll need, | ||
depending on your requirements. | ||
```terminal | ||
cargo run -p firehose-protos-examples --example receipt_root | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,32 +1,5 @@ | ||
// Copyright 2024-, Semiotic AI, Inc. | ||
// SPDX-License-Identifier: Apache-2.0 | ||
|
||
//! # Firehose Protos Examples | ||
//! | ||
//! Examples that use methods implemented on the Rust-compiled Firehose | ||
//! protobuffer types from [Firehose Protos](../firehose_protos/index.html). | ||
//! | ||
//! ## Running Examples | ||
//! | ||
//! To run the examples, you need access to a Firehose provider for each chain from which you want | ||
//! to extract data - an endpoint and an API key (if the latter is required). | ||
//! | ||
//! If you need access to a Firehose provider, we suggest using [Pinax](https://app.pinax.network/). | ||
//! | ||
//! Add your endpoint and API key to a `.env` file in the root of the repository. See `.env.examples` for | ||
//! a configuration template. | ||
//! | ||
//! To run individual examples, use the following command: | ||
//! | ||
//! ```terminal | ||
//! cargo run -p firehose-protos-examples --example <example_name> | ||
//! ``` | ||
//! | ||
//! So, for example, to run the `receipt_root` example: | ||
//! | ||
//! ```terminal | ||
//! cargo run -p firehose-protos-examples --example receipt_root | ||
//! ``` | ||
//! | ||
|
||
#![deny(missing_docs)] | ||
#![doc = include_str!("../README.md")] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Empty file.
Empty file.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.