You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+24-2Lines changed: 24 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,6 +51,30 @@ Check how to export handlers with [Matchstick - Test Coverage documentation](htt
51
51
> [!NOTE]
52
52
> Since Matchstick code coverage is in very early stages, Matchstick cannot check for branch coverage, but rely on the assertion that a given handler has been called.
53
53
54
+
## Deployment Options
55
+
56
+
### Thegraph network
57
+
58
+
To deploy this subgraph on Thegraph network:
59
+
60
+
1. Set up your environment variables in `.env` file:
61
+
62
+
```bash
63
+
SUBGRAPH_SLUG=your-subgraph-slug
64
+
SUBGRAPH_DEPLOY_KEY=your-deploy-key
65
+
SUBGRAPH_NETWORK_NAME=your-network-name
66
+
VERSION_LABEL=your-version-label
67
+
```
68
+
69
+
2. Deploy using the npm script:
70
+
71
+
```bash
72
+
npm run deploy-studio
73
+
```
74
+
75
+
### Self-Hosted Subgraph Deployment Process
76
+
77
+
54
78
## Docker subgraph deployer
55
79
56
80
The subgraph is deploy via a generated Docker image.
@@ -134,8 +158,6 @@ choice(
134
158
)
135
159
```
136
160
137
-
The deployment process will automatically generate the appropriate subgraph configuration using the network-specific addresses and start blocks from `networks.json`.
138
-
139
161
## Changelog
140
162
141
163
Changes to this project are tracked in [CHANGELOG.md](./CHANGELOG.md)
0 commit comments