Skip to content

Commit

Permalink
Added Subgraph Publishing document (#530)
Browse files Browse the repository at this point in the history
* Update sidebar.ts

* Added subgraph images

* Create publish-subgraph.md
  • Loading branch information
Danielvul authored Jun 19, 2024
1 parent 08758ee commit 56957ad
Show file tree
Hide file tree
Showing 4 changed files with 8 additions and 4 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 8 additions & 4 deletions docs/subquery_network/architects/publish-subgraph.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,9 @@ The SubQuery Network is the future of web3 infrastructure, it allows you to comp

## Prerequisites for your Subgraph project running on the Network

- You must have generated a unique IPFS CID for your SubGraph.
1. The SubQuery Network does not support GraphQL subscriptions
2. Your project can generate stable proof of indexing results. Node Operator’s proof of indexing will be kept private
3. You must have generated a unique IPFS CID for your SubGraph.

## Deploying your Subgraph Project

Expand All @@ -26,7 +28,7 @@ The SubQuery Network is a public permission-less network, anyone can deploy thei

You will need to publish your Subgraph project to IPFS first. Please enter the project CID and give your project a nice name.

![Publish - Enter CID and Name](/assets/img/network/architect_publish_ipfs.png)
![Publish - Enter CID and Name](/assets/img/network/architect_publish_subgraph.png)

On the next page you are asked to enter a project description, and also populate information about the project that Consumers or Node Operators might find interesting. This includes:

Expand All @@ -50,7 +52,7 @@ At this stage you should reach out to Node Operators in our Discord to encourage

You can easily make changes to your project or deploy a new version by accessing the Managed Project page.

![Manage Existing Project](/assets/img/network/architect_manage_project.png)
![Manage Existing Project](/assets/img/network/architect_manage_subgraph_project.png)

Firstly, you can publish a new version by clicking "Deploy New Version". This will let Node Operators know and allow them to upgrade to the new version of your Project. For the deployment you should provide:

Expand All @@ -59,6 +61,8 @@ Firstly, you can publish a new version by clicking "Deploy New Version". This wi
- check the box if you want to make this version recommended, this means that you are recommending Node Operators to immediately update to it. Don't check this if it's a test build or if it has major breaking changes
- the deployment description, which might include additional information for Node Operators about migration steps or breaking changes in this version

![Manage Existing Project - Deploy New Version](/assets/img/network/architect_manage_subgraph_project_deploy.png)

## Connect your dApp

To get started, create a Flex Plan and get your GraphQL endpoint [follow the guide here](../consumers/plan.md)
To get started, create a Flex Plan and get your GraphQL endpoint [follow the guide here](../consumers/plan.md)

0 comments on commit 56957ad

Please sign in to comment.