Skip to content

Commit 619e904

Browse files
enoldevbenface
andauthored
Remove Firehose clone (#517)
Co-authored-by: Benoît Rouleau <benoit.rouleau@icloud.com>
1 parent 77c0670 commit 619e904

34 files changed

+77
-231
lines changed

nginx.conf

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,10 +87,11 @@ http {
8787
rewrite ^/docs/([a-zA-Z][a-zA-Z])/arbitrum-faq/$ $scheme://$http_host/docs/$1/arbitrum/arbitrum-faq/ permanent;
8888
rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/migrating-a-subgraph/$ $scheme://$http_host/docs/$1/cookbook/upgrading-a-subgraph/ permanent;
8989
rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/quick-start/$ $scheme://$http_host/docs/$1/quick-start/ permanent;
90-
rewrite ^/docs/en/substreams/(.+)$ https://substreams.streamingfast.io permanent;
90+
rewrite ^/docs/en/substreams/(.+)$ https://substreams.streamingfast.io permanent;
91+
rewrite ^/docs/en/firehose/(.+)$ https://firehose.streamingfast.io permanent;
92+
9193

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

9697
location / {

website/next.config.js

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -56,11 +56,6 @@ export default withNextra({
5656
destination: '/en/arbitrum/arbitrum-faq/',
5757
permanent: true,
5858
},
59-
{
60-
source: '/en/firehose/',
61-
destination: '/en/firehose/README/',
62-
permanent: false,
63-
},
6459
{
6560
source: '/en/querying/graph-client/',
6661
destination: '/en/querying/graph-client/README/',

website/pages/ar/new-chain-integration.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ If the blockchain is EVM equivalent and the client/node exposes the standard EVM
1919

2020
**2. Firehose**
2121

22-
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.
22+
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.
2323

2424
## Difference between EVM JSON-RPC & Firehose
2525

@@ -71,5 +71,5 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give
7171
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:
7272

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

website/pages/cs/new-chain-integration.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ If the blockchain is EVM equivalent and the client/node exposes the standard EVM
1919

2020
**2. Firehose**
2121

22-
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.
22+
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.
2323

2424
## Difference between EVM JSON-RPC & Firehose
2525

@@ -71,5 +71,5 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give
7171
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:
7272

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

website/pages/de/new-chain-integration.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ If the blockchain is EVM equivalent and the client/node exposes the standard EVM
1919

2020
**2. Firehose**
2121

22-
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.
22+
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.
2323

2424
## Difference between EVM JSON-RPC & Firehose
2525

@@ -71,5 +71,5 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give
7171
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:
7272

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

website/pages/en/_meta.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ export default {
4343
'operating-graph-node': '',
4444
'chain-integration-overview': '',
4545
'new-chain-integration': 'Integrating New Networks',
46-
firehose: 'Firehose',
46+
firehose: '',
4747
graphcast: '',
4848
'mips-faqs': '',
4949
}

website/pages/en/firehose.mdx

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
title: Firehose
3+
---
4+
5+
![Firehose Logo](/img/firehose-logo.png)
6+
7+
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.
8+
9+
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.
10+
11+
## Firehose Documentation
12+
13+
The Firehose documentation is currently maintained by the StreamingFast team [on the StreamingFast website](https://firehose.streamingfast.io).
14+
15+
### Getting Started
16+
17+
- Read this [Firehose introduction](https://firehose.streamingfast.io/introduction/firehose-overview) to get an overview of what it is and why it was built.
18+
- Learn about the [Prerequisites](https://firehose.streamingfast.io/introduction/prerequisites) to install and deploy Firehose.
19+
20+
### Expand Your Knowledge
21+
22+
- Learn about the different [Firehose components](https://firehose.streamingfast.io/architecture/components) available.

website/pages/en/firehose/[[...slug]].mdx

Lines changed: 0 additions & 51 deletions
This file was deleted.

website/pages/en/firehose/_meta.js

Lines changed: 0 additions & 91 deletions
This file was deleted.

website/pages/en/new-chain-integration.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ If the blockchain is EVM equivalent and the client/node exposes the standard EVM
1919

2020
**2. Firehose**
2121

22-
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:integrations@streamingfast.io) if you need help with Firehose development.
22+
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:integrations@streamingfast.io) if you need help with Firehose development.
2323

2424
## Difference between EVM JSON-RPC & Firehose
2525

@@ -71,5 +71,5 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give
7171
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:
7272

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

0 commit comments

Comments
 (0)