Skip to content

Commit

Permalink
Remove Firehose clone (#517)
Browse files Browse the repository at this point in the history
Co-authored-by: Benoît Rouleau <[email protected]>
  • Loading branch information
enoldev and benface authored Sep 28, 2023
1 parent 77c0670 commit 619e904
Show file tree
Hide file tree
Showing 34 changed files with 77 additions and 231 deletions.
5 changes: 3 additions & 2 deletions nginx.conf
Original file line number Diff line number Diff line change
Expand Up @@ -87,10 +87,11 @@ http {
rewrite ^/docs/([a-zA-Z][a-zA-Z])/arbitrum-faq/$ $scheme://$http_host/docs/$1/arbitrum/arbitrum-faq/ permanent;
rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/migrating-a-subgraph/$ $scheme://$http_host/docs/$1/cookbook/upgrading-a-subgraph/ permanent;
rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/quick-start/$ $scheme://$http_host/docs/$1/quick-start/ permanent;
rewrite ^/docs/en/substreams/(.+)$ https://substreams.streamingfast.io permanent;
rewrite ^/docs/en/substreams/(.+)$ https://substreams.streamingfast.io permanent;
rewrite ^/docs/en/firehose/(.+)$ https://firehose.streamingfast.io permanent;


# Temporary redirects (302)
rewrite ^/docs/en/firehose/$ $scheme://$http_host/docs/en/firehose/README/ redirect;
rewrite ^/docs/en/querying/graph-client/$ $scheme://$http_host/docs/en/querying/graph-client/README/ redirect;

location / {
Expand Down
5 changes: 0 additions & 5 deletions website/next.config.js
Original file line number Diff line number Diff line change
Expand Up @@ -56,11 +56,6 @@ export default withNextra({
destination: '/en/arbitrum/arbitrum-faq/',
permanent: true,
},
{
source: '/en/firehose/',
destination: '/en/firehose/README/',
permanent: false,
},
{
source: '/en/querying/graph-client/',
destination: '/en/querying/graph-client/README/',
Expand Down
4 changes: 2 additions & 2 deletions website/pages/ar/new-chain-integration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ If the blockchain is EVM equivalent and the client/node exposes the standard EVM

**2. Firehose**

For non-EVM-based chains, Graph Node will need to ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/README/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach.
For non-EVM-based chains, Graph Node will need to ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach.

## Difference between EVM JSON-RPC & Firehose

Expand Down Expand Up @@ -71,5 +71,5 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give
Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:

1. [General docs on Firehose](firehose/)
2. [Adding Firehose support for a new chain](firehose/integrate-new-chains/new-blockchains/)
2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
4 changes: 2 additions & 2 deletions website/pages/cs/new-chain-integration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ If the blockchain is EVM equivalent and the client/node exposes the standard EVM

**2. Firehose**

For non-EVM-based chains, Graph Node will need to ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/README/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach.
For non-EVM-based chains, Graph Node will need to ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach.

## Difference between EVM JSON-RPC & Firehose

Expand Down Expand Up @@ -71,5 +71,5 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give
Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:

1. [General docs on Firehose](firehose/)
2. [Adding Firehose support for a new chain](firehose/integrate-new-chains/new-blockchains/)
2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
4 changes: 2 additions & 2 deletions website/pages/de/new-chain-integration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ If the blockchain is EVM equivalent and the client/node exposes the standard EVM

**2. Firehose**

For non-EVM-based chains, Graph Node will need to ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/README/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach.
For non-EVM-based chains, Graph Node will need to ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach.

## Difference between EVM JSON-RPC & Firehose

Expand Down Expand Up @@ -71,5 +71,5 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give
Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:

1. [General docs on Firehose](firehose/)
2. [Adding Firehose support for a new chain](firehose/integrate-new-chains/new-blockchains/)
2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
2 changes: 1 addition & 1 deletion website/pages/en/_meta.js
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ export default {
'operating-graph-node': '',
'chain-integration-overview': '',
'new-chain-integration': 'Integrating New Networks',
firehose: 'Firehose',
firehose: '',
graphcast: '',
'mips-faqs': '',
}
22 changes: 22 additions & 0 deletions website/pages/en/firehose.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
title: Firehose
---

![Firehose Logo](/img/firehose-logo.png)

Firehose is a new technology developed by StreamingFast working with The Graph Foundation. The product provides **previously unseen capabilities and speeds for indexing blockchain data** using a files-based and streaming-first approach.

Firehose extracts, transforms and saves blockchain data in a highly performant file-based strategy. Blockchain developers can then access data extracted by Firehose through binary data streams. Firehose is intended to stand as a replacement for The Graph’s original blockchain data extraction layer.

## Firehose Documentation

The Firehose documentation is currently maintained by the StreamingFast team [on the StreamingFast website](https://firehose.streamingfast.io).

### Getting Started

- Read this [Firehose introduction](https://firehose.streamingfast.io/introduction/firehose-overview) to get an overview of what it is and why it was built.
- Learn about the [Prerequisites](https://firehose.streamingfast.io/introduction/prerequisites) to install and deploy Firehose.

### Expand Your Knowledge

- Learn about the different [Firehose components](https://firehose.streamingfast.io/architecture/components) available.
51 changes: 0 additions & 51 deletions website/pages/en/firehose/[[...slug]].mdx

This file was deleted.

91 changes: 0 additions & 91 deletions website/pages/en/firehose/_meta.js

This file was deleted.

4 changes: 2 additions & 2 deletions website/pages/en/new-chain-integration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ If the blockchain is EVM equivalent and the client/node exposes the standard EVM

**2. Firehose**

For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/README/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:[email protected]) if you need help with Firehose development.
For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:[email protected]) if you need help with Firehose development.

## Difference between EVM JSON-RPC & Firehose

Expand Down Expand Up @@ -71,5 +71,5 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give
Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:

1. [General docs on Firehose](firehose/)
2. [Adding Firehose support for a new chain](firehose/integrate-new-chains/new-blockchains/)
2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
2 changes: 2 additions & 0 deletions website/pages/en/substreams.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@
title: Substreams
---

![Substreams Logo](/img/substreams-logo.png)

Substreams is a powerful blockchain indexing technology, developed for The Graph Network. Substreams enables developers to write Rust modules, composing data streams alongside the community, and provides extremely high-performance indexing by virtue of parallelization, in a streaming-first fashion.

With Substreams, you can extract data from different blockchains (Ethereum, BNB, Solana...) ultra-fast! Then, you can send to data to several locations (a Postgres database, a Mongo database, or a Subgraph).
Expand Down
4 changes: 2 additions & 2 deletions website/pages/es/new-chain-integration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ If the blockchain is EVM equivalent and the client/node exposes the standard EVM

**2. Firehose**

For non-EVM-based chains, Graph Node will need to ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/README/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach.
For non-EVM-based chains, Graph Node will need to ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach.

## Difference between EVM JSON-RPC & Firehose

Expand Down Expand Up @@ -71,5 +71,5 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give
Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:

1. [General docs on Firehose](firehose/)
2. [Adding Firehose support for a new chain](firehose/integrate-new-chains/new-blockchains/)
2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
4 changes: 2 additions & 2 deletions website/pages/fr/new-chain-integration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ If the blockchain is EVM equivalent and the client/node exposes the standard EVM

**2. Firehose**

For non-EVM-based chains, Graph Node will need to ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/README/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach.
For non-EVM-based chains, Graph Node will need to ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach.

## Difference between EVM JSON-RPC & Firehose

Expand Down Expand Up @@ -71,5 +71,5 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give
Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:

1. [General docs on Firehose](firehose/)
2. [Adding Firehose support for a new chain](firehose/integrate-new-chains/new-blockchains/)
2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
Loading

0 comments on commit 619e904

Please sign in to comment.