Skip to content

Revamp the toplevel and the docker README #5979

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
May 9, 2025
Merged

Revamp the toplevel and the docker README #5979

merged 5 commits into from
May 9, 2025

Conversation

lutter
Copy link
Collaborator

@lutter lutter commented Apr 30, 2025

These were woefully out of date and utterly confusing

@lutter
Copy link
Collaborator Author

lutter commented May 1, 2025

@alex-pakalniskis @idalithb I would love your take on this, in particular the new README It's still a little too intimidating for my taste

@lutter lutter self-assigned this May 1, 2025
@fordN fordN requested review from alex-pakalniskis and fordN May 1, 2025 15:47
Copy link

@alex-pakalniskis alex-pakalniskis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for tackling this David. Updated docs are a huge improvement and we can further simplify once the local dev experience lands.

@idalithb idalithb self-requested a review May 8, 2025 23:16
Copy link

@idalithb idalithb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lutter This is awesome. Some of this is inherently a bit complicated, but I tried to provide a little more structure. Feel free to take or leave what you want. 😄

README.md Outdated
@@ -3,193 +3,113 @@
[![Build Status](https://github.com/graphprotocol/graph-node/actions/workflows/ci.yml/badge.svg)](https://github.com/graphprotocol/graph-node/actions/workflows/ci.yml?query=branch%3Amaster)
[![Getting Started Docs](https://img.shields.io/badge/docs-getting--started-brightgreen.svg)](docs/getting-started.md)

[The Graph](https://thegraph.com/) is a protocol for building decentralized applications (dApps) quickly on Ethereum and IPFS using GraphQL.
[The Graph](https://thegraph.com/) is a protocol that organizes and serves web3 data.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
[The Graph](https://thegraph.com/) is a protocol that organizes and serves web3 data.
## Overview
[The Graph](https://thegraph.com/) is decentralized protocol that organizes and distributes blockchain data across the leading Web3 networks. A key component of The Graph's tech stack is Graph Node.

README.md Outdated
Comment on lines 10 to 14
You can find more details on how to write these transformations, called
_subgraphs_, in the official [Graph
documentation](https://thegraph.com/docs/en/subgraphs/quick-start/). If you
are not familiar already with subgraphs, we highly recommend at least
reading through that documentation first.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
You can find more details on how to write these transformations, called
_subgraphs_, in the official [Graph
documentation](https://thegraph.com/docs/en/subgraphs/quick-start/). If you
are not familiar already with subgraphs, we highly recommend at least
reading through that documentation first.
Before using `graph-node,` it's highly recommended that you read the [official Graph documentation]((https://thegraph.com/docs/en/subgraphs/quick-start/) to understand Subgraphs, which are schema-driven APIs.

README.md Outdated

For detailed instructions and more context, check out the [Getting Started Guide](docs/getting-started.md).
The rest of this page is geared towards two audiences:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The rest of this page is geared towards two audiences:
This guide is for:
1. Subgraph developers who want to run `graph-node` locally to test their Subgraphs during development
2. Contributors who want to add features or fix bugs to `graph-node` itself

README.md Outdated
Comment on lines 18 to 21
1. Subgraph developers who want to run `graph-node` locally so they can test
their subgraphs during development
2. Developers who want to contribute bug fixes and features to `graph-node`
itself
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Subgraph developers who want to run `graph-node` locally so they can test
their subgraphs during development
2. Developers who want to contribute bug fixes and features to `graph-node`
itself

their subgraphs during development
2. Developers who want to contribute bug fixes and features to `graph-node`
itself

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Local Set Up

Ethereum network name (e.g. 'mainnet'), optional comma-separated capabilities (eg full,archive), and an Ethereum IPC pipe, separated by a ':'
When `graph-node` starts, it prints the various ports that it is listening on.
The most important of these is the GraphQL HTTP server, which is by default
is at `http://localhost:8000`. You can use routes like `/subgraphs/name/<subgraph-name>`
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
is at `http://localhost:8000`. You can use routes like `/subgraphs/name/<subgraph-name>`
at `http://localhost:8000`.
You can use routes like `/subgraphs/name/<subgraph-name>`

README.md Outdated
--subgraph <[NAME:]IPFS_HASH> Name and IPFS hash of the subgraph manifest
--ws-port <PORT> Port for the GraphQL WebSocket server [default: 8001]
```
Instructions for how to deploy subgraphs can be found [here](https://thegraph.com/docs/en/subgraphs/developing/introduction/) After setting up `graph-cli` as described there, you can deploy a subgraph to your local Graph Node instance.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Instructions for how to deploy subgraphs can be found [here](https://thegraph.com/docs/en/subgraphs/developing/introduction/) After setting up `graph-cli` as described there, you can deploy a subgraph to your local Graph Node instance.
Follow the [Subgraph deployment guide](https://thegraph.com/docs/en/subgraphs/developing/introduction/). After setting up `graph-cli` as described, you can deploy a Subgraph to your local Graph Node instance.


Very large `graph-node` instances can also be configured using a
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Very large `graph-node` instances can also be configured using a
> Please note: Very large `graph-node` instances can also be configured using a

README.md Outdated

Graph Node is an open source Rust implementation that event sources the Ethereum blockchain to deterministically update a data store that can be queried via the GraphQL endpoint.
Graph Node extracts and transforms blockchain data and makes the transformed
data available to decentralized applications (dApps) via GraphQL queries.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
data available to decentralized applications (dApps) via GraphQL queries.
data available to decentralized applications (dapps) via GraphQL queries.

README.md Outdated

### Prerequisites

To build and run this project you need to have the following installed on your system:

- Rust (latest stable) – [How to install Rust](https://www.rust-lang.org/en-US/install.html)
- Note that `rustfmt`, which is part of the default Rust installation, is a build-time requirement.
- PostgreSQL – [PostgreSQL Downloads](https://www.postgresql.org/download/)
has general instructions. Run `rustup install stable` in this directory to make
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
has general instructions. Run `rustup install stable` in this directory to make
Run `rustup install stable` in this directory to make

lutter added 5 commits May 8, 2025 18:10
These were woefully out of date and utterly confusing
That file is way out of date and duplicate the official documentation on
thegraph.com
@lutter
Copy link
Collaborator Author

lutter commented May 9, 2025

@idalithb Thanks a ton for the detailed review. I've incorporated most of your suggestions - thanks so much for turning this into actual English ;)

@lutter lutter merged commit 86c61b4 into master May 9, 2025
6 checks passed
@lutter lutter deleted the lutter/docs branch May 9, 2025 01:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants