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
+37Lines changed: 37 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,6 +114,43 @@ docker run --rm \
114
114
poco-subgraph-deployer
115
115
```
116
116
117
+
#### Manual Deployment with Custom Values
118
+
119
+
To deploy the subgraph manually using the deploy script, follow these steps:
120
+
121
+
1. Set up environment variables in the `.env` file:
122
+
123
+
```bash
124
+
NETWORK_NAME=<network-name>
125
+
DEPLOY_ENV=<deploy-environment>
126
+
IPFS_URL=<ipfs-url>
127
+
GRAPHNODE_URL=<graphnode-url>
128
+
VERSION_LABEL=<version-label>
129
+
```
130
+
131
+
Example:
132
+
133
+
```bash
134
+
NETWORK_NAME=bellecour
135
+
DEPLOY_ENV=staging
136
+
IPFS_URL=http://localhost:5001
137
+
GRAPHNODE_URL=http://localhost:8020
138
+
VERSION_LABEL=1.0.0
139
+
```
140
+
141
+
**DEPLOY_ENV Possible Values:**
142
+
-`empty`: For production deployment.
143
+
-`tmp`: For temporary indexing and avoiding downtime during production deployment.
144
+
-`staging`: For staging environment deployment.
145
+
146
+
2. Run the deploy script:
147
+
148
+
```bash
149
+
npm run deploy
150
+
```
151
+
152
+
This will deploy the subgraph using the specified values, including the `DEPLOY_ENV` variable for environment-specific configurations.
153
+
117
154
#### Github Actions pipeline deployment
118
155
119
156
The subgraph can be deployed using Github Actions (recommended). The dedicated job can be triggered with the desired configuration (environment, version, ...).
0 commit comments