本文从团队开发 the Graph 利用 subgraph 的场景为背景，介绍其环境的搭建：线下开发的机器比较复杂就以 mac 机器为例一步一步配置解说，线上环境属于比拟洁净但辅助软件欠缺，须要从头部署，读者能够按需浏览。
The Graph 开发环境搭建
Ganache 部署
除了本地部署官网文档，还有这篇介绍本地部署的文档
NPM/Yarn 全局装置 truffle ganache-cli
$ npm install -g truffle ganache-cli
or
$ yarn global add truffle ganache-cliganache-cli 启动
$ ganache-cli -h 0.0.0.0
Ganache CLI v6.12.2 (ganache-core: 2.13.2)
Available Accounts
=
(0) 0x373548217c1C6d3F896833418cCDc14426BE91cd (100 ETH)
(1) 0x65f77651165C132252ea43E34f3aE24048216ce8 (100 ETH)
(2) 0x1861c71ABC4Ccd4990bb42638C4966e9012A8fc9 (100 ETH)
(3) 0x919A60B34B05feCdB712301120677236B9a3FadE (100 ETH)
(4) 0x7C9E7100d4EA8B25Af4c56aBcf1E2C854e7c363E (100 ETH)
(5) 0xD5f03B34884F57bC9b1E4be4dA6c65c0b5ed8d0e (100 ETH)
(6) 0x79919c9e8832317c0757734C8F01164bBba1B6E3 (100 ETH)
(7) 0xCf135Fa7F9c77Ba5251B55E4A2D6F27f337f4A32 (100 ETH)
(8) 0xfD17D90c6C85C91fd0B81d65964336BC924A0113 (100 ETH)
(9) 0x7887465f89eD278960a55Bf6e391b61528747A60 (100 ETH)
Private Keys
=
(0) 0xa9b479e9304251d7f2f4dfcbc143fd037cfdb02fc3bb70f6826297bc4206b945
(1) 0x0feef1514167b7c1b4cdc11e5d8eb407ab4d04661771f3efc9ccc185c0103ee0
注：带参数的启动能够再现大部分历史环境
例如：ganache-cli -h 0.0.0.0 -v /db -b 6 -a 8 -e 1000 -d expect chair toe trade spider wedding say item scare fog shrimp garlic
关上存在库，设置主动挖矿工夫 6，设置 8 个 1000gas 账号，导入现有私钥，（-d，能够是里面，也可用 - m 产生）
拉 graph-node（本级简单的环境历程）
下载 https://download.docker.com/m…，装置放入 APP 中，运行并输出明码，命令行可用。
所有看起十分失常，然而后续装置可能会产生各种问题，因你的本机软硬件环境而异，但都须要平常心对之。
$ brew install jq
$ docker -vbrew install 装置更新出师不利，填坑见 brew upgrade 装置报错 解决 brew upgrade mac 更新组件遗留问题。
Docker version 20.10.5, build 55c4c88 还 ok。
拉 graph-node 节点
$ git clone https://github.com/graphprotocol/graph-node/此处 git 等常见人力不可达地区资源坑见 代理与镜像坑 有时候重复多试试就过来了，过来了就保重劳动成果，备份一些资源，未来有不可抗力时能够把这些文件 复制 / 粘贴（或者间接利用你共事的洁净环境获取本地文件，回头再解决你的环境问题）
配置启动 the Graph
$ cd graph-node/docker
$ ./setup.sh #write the host IP address into docker-compose.yml.
$ docker-compose up #Start a local Graph Node that will connect to Ganache on your hostgraph-node_1 | Jun 22 11:13:56.395 INFO Starting JSON-RPC admin server at: http://localhost:8020, component: JsonRpcServer
graph-node_1 | Jun 22 11:13:56.395 INFO Started all subgraphs, component: SubgraphRegistrar
graph-node_1 | Jun 22 11:13:56.397 INFO Starting GraphQL HTTP server at: http://localhost:8000, component: GraphQLServer
graph-node_1 | Jun 22 11:13:56.397 INFO Starting index node server at: http://localhost:8030, component: IndexNodeServer
graph-node_1 | Jun 22 11:13:56.399 INFO Starting GraphQL WebSocket server at: ws://localhost:8001, component: SubscriptionServer
graph-node_1 | Jun 22 11:13:56.399 INFO Starting metrics server at: http://localhost:8040, component: MetricsServer
启动 docker-compose up
时报错是因为拜访 host IP 导致 解决
敞开节点 docker-compose down -v;
docker-compose down -v;
if [-d”data”] thenecho”Found old data for the graph node – deleting it”; # we need to sudo this to remove system locked filessudorm-rf data/;
fi
客户端 graphprotocol/graph-cli 装置
$ npm install -g @graphprotocol/graph-cli
$ graph init --from-example moluoping/mark-cion
#graph init --from-example <GITHUB_USERNAME>/<SUBGRAPH_NAME> [<DIRECTORY>]产生的 yarn 性能 lock 文件锁住了依赖包的版本，也锁住了源 url 不能用镜像
解决：备份 lock，应用 npm 拉下所有包（淘宝镜像不全，应用官网 http://registry.npmjs.org/）
（比拟版本依赖）资源坑见 代理与镜像坑
下面是通过例子生产合约和 subgraph
还能够间接从容器中合约向导生成 subgraph 工程：
$ graph init --from-contract 0x1e1215caD01aD7192832e0DACfA930Caf0132b43 --network mainnet --abi markdemo4.json moluoping/markdemo4编译 & 部署合约
编译与全新编译
$ truffle compile
（truffle compile –all 全新编译
https://www.trufflesuite.com/…）Compiling your contracts…
✔ Fetching solc version list from solc-bin. Attempt #1
✔ Downloading compiler. Attempt #1.
Compiling ./contracts/Gravity.sol
Compiling ./contracts/Migrations.sol
Artifacts written to /Users/gaoxiaoqing/Documents/swork/feature/markggg/build/contracts
Compiled successfully using:
solc: 0.4.25+commit.59dbf8f1.Emscripten.clang
公布与重新部署
$ truffle migrate
(truffle migrate –reset 重新部署 https://www.trufflesuite.com/…
Network name: ‘development’
Network id: 1624441310514
Block gas limit: 6721975 (0x6691b7)
1_initial_migration.js
Deploying ‘Migrations’
transaction hash: 0x92950fa746934bed8f1af3e1ea915c76669858c7e9b396c1dfa74276cfdb2745
Blocks: 0 Seconds: 0
contract address: 0x0A994866b43562c083C81E1B4AD6145214f56c56
block number: 1
block timestamp: 1624441330
监听合约通过合约 Id，配置
$ sed -i -e 's/0x2E645469f354BB4F5c8a05B3b30A929361cf77eC/0x71e11bC372507d508E05f65c096d32F1eF62Cdf7/g' subgraph.yaml
$ sed -i -e 's/0x2E645469f354BB4F5c8a05B3b30A929361cf77eC/0x0A994866b43562c083C81E1B4AD6145214f56c56/g' subgraph.yaml此处犯一低级谬误，第二个合约才是真正无效的，但第二指令为达到成果
sed -i -e ‘s/0x2E645469f354BB4F5c8a05B3b30A929361cf77eC/0x0A994866b43562c083C81E1B4AD6145214f56c56/g’ subgraph.yaml
应该改为
sed -i -e ‘s/0x71e11bC372507d508E05f65c096d32F1eF62Cdf7/0x0A994866b43562c083C81E1B4AD6145214f56c56/g’ subgraph.yaml
因为第一次命令曾经替换了文本
编译、创立 subgarph，公布 the graph App
下载依赖包，编译
$ yarn && yarn codegen
改成 $npm install
$yarn codegen
该计划长期获得依赖实现后续工作，ok 后解决环境问题见 代理与镜像坑
✔ Load subgraph from subgraph.yaml
Load contract ABI from abis/Gravity.json
✔ Load contract ABIs
Generate types for contract ABI: Gravity (abis/Gravity.json)
Write types to generated/Gravity/Gravity.ts
✔ Generate types for contract ABIs
✔ Generate types for data source templates
✔ Load data source template ABIs
✔ Generate types for data source template ABIs
✔ Load GraphQL schema from schema.graphql
Write types to generated/schema.ts
✔ Generate types for GraphQL schema
Types generated successfully
创立 subgarph，公布之
$ yarn create-local
$ yarn deploy-local$ yarn create-local
graph create moluoping/markg –node http://127.0.0.1:8020
Created subgraph: moluoping/markg
$ yarn deploy-local
✔ Write compiled subgraph to build/
Add file to IPFS build/schema.graphql
.. QmbSFRGGvHM7Cn8YSjDL41diDMxN4LQUDEMqaa5VVc5sC4
Add file to IPFS build/Gravity/abis/Gravity.json
.. QmajZTadknSpgsCWRz9fG6bXFHdpVXPMWpx9yMipz3VtMQ
Add file to IPFS build/Gravity/Gravity.wasm
.. QmbK8bwncci52cstF3P8Q8i4oGjrMt1pUqdv5Uf1VXqXdb
✔ Upload subgraph to IPFS
Build completed: Qmd77mi1ATxscqsBvLANrw9gP1dJNsQMTexvErw5XVyFLc
✖ Failed to deploy to Graph node http://127.0.0.1:8020/: Ethereum network not supported by registrar: mainnet
error Command failed with exit code 1.
找到 docker/docker-compose.yml-e 的 ethereum:’mainnet:http://host.docker.internal:8545′
批改为本地：ethereum: ‘mainnet:http://192.168.0.136:8545’
✔ Upload subgraph to IPFS
Build completed: QmYNgbF7YfDs6Y8YV7aqYGS7cVx5vpt1uNhk3y7wmkAUgm
Deployed to http://127.0.0.1:8000/subgrap…
Subgraph endpoints:
Queries (HTTP): http://127.0.0.1:8000/subgrap…
Subscriptions (WS): http://127.0.0.1:8001/subgrap…
✨ Done in 21.16s.
8001 端口与 Vray http 代理端口抵触，批改 Vray http 代理端口为 8701，顺便把 git clone 和 yarn 下载的代理问题解决
代理与镜像坑点
特地留神 8001 端口与 Vray http 代理端口抵触
批改 Vray http 代理端口为 8701，顺便把 git clone 和 yarn 下载的代理问题解决
特地留神代理，代理，代理
咱们不在代理，就在镜像的路上，有时候 git 和 yarn 还是会报同步错，这时候能够重复如下操作
git config --global http.proxy socks5://127.0.0.1:1080
git config --global https.proxy socks5://127.0.0.1:1080
git config --global https.proxy http://127.0.0.1:1080
git config --global https.proxy https://127.0.0.1:1080
git config --global --unset http.proxy
git config --global --unset https.proxy
开关 / 开关代理
NPM
查问以后镜像
npm get registry
设置为淘宝镜像
npm config set registry https://registry.npm.taobao.org/
设置为官网镜像
npm config set registry https://registry.npmjs.org/
YARN
查问以后镜像
yarn config get registry
设置为淘宝镜像
yarn config set registry https://registry.npm.taobao.org/
设置为官网镜像
yarn config set registry https://registry.yarnpkg.com阿里和官网不停切换
brew upgrade 装置报错问题解决替换 homebrew-bottles
$ brew upgrade
或者
$ 任何须要更新的命令
所以必须解决==>Installing libtool dependency: m4
==>Pouring m4-1.4.18.mojave.bottle.1.tar.gz
tar: Error opening archive: Failed to open ‘/Users/gaoxiaoqing/Library/Caches/Homebrew/downloads/f25291efa07f91502eda2b4c0bd6fa41fae3c19661fa239d3855027f9c0a36d1–m4-1.4.18.mojave.bottle.1.tar.gz’
Error: Failure while executing; tar --extract --no-same-owner --file /Users/gaoxiaoqing/Library/Caches/Homebrew/downloads/f25291efa07f91502eda2b4c0bd6fa41fae3c19661fa239d3855027f9c0a36d1--m4-1.4.18.mojave.bottle.1.tar.gz --directory /private/tmp/d20210628-40770-hpzxk9 exited with 1. Here’s the output:
tar: Error opening archive: Failed to open ‘/Users/gaoxiaoqing/Library/Caches/Homebrew/downloads/f25291efa07f91502eda2b4c0bd6fa41fae3c19661fa239d3855027f9c0a36d1–m4-1.4.18.mojave.bottle.1.tar.gz’
计划一：替换文件
找到 /Users/gaoxiaoqing/Library/Caches/Homebrew/downloads/ 发现有 66ff350c21fce7c264e33e3cff6f4995978ac401d5e5047c0ee8dd17e3493a53–m4-1.4.18.mojave.bottle.1.tar.gz，改名。ok，我预计是有两个或两个版本用到这个，前面一个就缓存不生成了，然而忙过当前还是睡不着啊，有了第二种解决方案。
计划二：替换 homebrew-bottles
echo 'export HOMEBREW_BOTTLE_DOMAIN=https://mirrors.ustc.edu.cn/homebrew-bottles' >> ~/.bash_profile
source ~/.bash_profilebrew 包含四块
| Homebrew | 源代码仓库 |
|---|---|
| homebrew-core | Homebrew 外围源 |
| homebrew-cask | 提供 macos 利用和大型二进制文件的装置 |
| homebrew-bottles | 预编译二进制软件包 |
如果用到也同样可改镜像
$ git -C "$(brew --repo)" remote set-url origin https://mirrors.ustc.edu.cn/brew.git
$ git -C "$(brew --repo homebrew/core)" remote set-url origin https://mirrors.ustc.edu.cn/homebrew-core.git
$ git -C "$(brew --repo homebrew/cask)" remote set-url origin https://mirrors.ustc.edu.cn/homebrew-cask.git配置文件脚本主动替换坑
数据源获取不精确
graph-node_1 | Jun 24 01:34:13.558 WARN Trying again after net_version RPC call failed (attempt #18) with result Err(Transport error: Error(Connect, Os { code: 111, kind: ConnectionRefused, message: “Connection refused”})), provider: mainnet-rpc-0
graph-node_1 | Jun 24 01:34:14.517 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: mainnet-rpc-0
该报错会引起后续（相关联利用）报错：
Failed to deploy to Graph node http://127.0.0.1:8020/: Ethereum network not supported by registrar: mainnet.
解决：ConnectionRefused 个别是对方服务器不能到达
找到 docker/docker-compose.yml-e 的 ethereum:’mainnet:http://host.docker.internal:8545′
批改为本地：ethereum: ‘mainnet:http://192.168.0.136:8545’
数据屡次替换源产生变更引起
合同调试工具
- Truffle Console: A basic interactive console connecting to any Ethereum client
- Truffle Develop: An interactive console that also spawns a development blockchain
https://www.trufflesuite.com/…
the Graph 线上服务器 & certos8 装置
装置线上服务器 docker & 启动
# sudo yum install -y yum-utils device-mapper-persistent-data lvm2
# sudo yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
# sudo yum install docker-ce docker-ce-cli containerd.io
# yum list docker-ce --showduplicates | sort -rdocker-ce.x86_64 3:20.10.7-3.el8 docker-ce-stable docker-ce.x86_64 3:20.10.7-3.el8 @docker-ce-stable
docker-ce.x86_64 3:20.10.6-3.el8 docker-ce-stable
docker-ce.x86_64 3:20.10.5-3.el8 docker-ce-stable
# sudo yum install docker-ce-20.10.7-3.el8 docker-ce-cli-20.10.7-3.el8 containerd.io
# sudo systemctl start docker拉下节点 graph-node & 配置启动
# git clone https://github.com/graphprotocol/graph-node/装置 docker-compose
# yum -y install epel-release
# yum install python3-pip）yum install python-pip（certos7）
# pip3 install --upgrade pip
# pip install docker-composepip3 install –upgrade pip（certos7）
若应用 pip install docker-compose 装置失败，则应用上面一条命令试试 #pip –default-timeout=200 install -U docker-compose
装置 install ‘jq’
# yum install jq
运行环境设置，重点关注 IP 地址 copy
# cd graph-node/docker
./setup.sh write the host IP address into docker-compose.yml. 如果 ip 不是你主机 ip，手动批改
docker: read tcp 192.168.7.235:36512->54.230.212.9:443: read: connection reset by peer.
应用下一节阿里云镜像减速解决
阿里云镜像减速
https://help.aliyun.com/docum…
应用 Docker 时须要首先下载一个官网镜像，例如mysql、wordpress。然而因为网络起因，下载一个 Docker 官网镜像可能会须要很长的工夫，甚至下载失败。为此，阿里云容器镜像服务 ACR 提供了官网的镜像站点，从而减速官网镜像的下载。镜像加速器是面向集体开发者的服务，仅限额反对集体开发场景，不容许有再次封装或商业用途。
# sudo mkdir -p /etc/docker
# sudo tee /etc/docker/daemon.json <<-'EOF'
{"registry-mirrors": ["https://de43k63h.mirror.aliyuncs.com"]
}
EOF
# sudo systemctl daemon-reload
# sudo systemctl restart dockerhttps://de43k63h.mirror.aliyu… 替换成你的镜像：对于加速器的地址，您登录容器镜像服务控制台后，在左侧导航栏抉择 镜像工具 > 镜像加速器 ，在 镜像加速器 页面就会显示为您独立调配的加速器地址。
持续./setup.sh 设置, 跟踪 IP 地址
Starting graph-node … doneHost IP: 172.18.0.1
# ifconfig
br-c3a270be10f6: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
inet6 fe80::42:b1ff:fea4:30eb prefixlen 64 scopeid 0x20<link>
ether 02:42:b1:a4:30:eb txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:76:73:7f:6c txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.31.XXX.XXX netmask 255.255.240.0 broadcast 172.31.191.255
inet6 fe80::216:3eff:fe02:a9a7 prefixlen 64 scopeid 0x20<link>
ether 00:16:3e:02:a9:a7 txqueuelen 1000 (Ethernet)
这里咱们手动批改 172.18.0.1 到近程的 以太坊容器 IP（docker/docker-compose.yml）
启动 the Graph
启动# docker-compose up
进行# docker-compose down -v
ok，能够应用了
http://47.100.XXX.XXX:8000
http://47.100.XXX.XXX:8001
http://47.100.XXX.XXX:8020
http://47.100.XXX.XXX:8040
进入 docker 日志
近程连贯再次进入日志查看
# docker ps
CONTAINER ID IMAGE COMMAND PORTS NAMESf8dea825ae05 graphprotocol/graph-node “/bin/sh -c start” 8040->8040/tcp docker_graph-node_1
890420a4b747 ipfs/go-ipfs:v0.4.23 “/sbin/tini — /usr/…” 5001->5001/tcp docker_ipfs_1
1e477194e786 postgres “docker-entrypoint.s…” 5432->5432/tcp
# docker logs --tail 10 f8dea825ae05
# docker logs --follow f8dea825ae05作者：Mark
欢送区块链行业气味相投的小伙伴增加小极微信，退出 blockgeek 区块链技术交换群，独特推动区块链技术遍及和倒退~