Graph definition for The LAO
Managing different network deployments for the contracts, is currently setup using config files in /config/, providing the addresses for each network:
For example, /config/local.json:
{
"network": "rinkeby",
"address": "0xeC43DfFaf01B6b03BAC5e2D93f8FE0D873b41Af8"
}
A template manifest subgraph.template.yaml has been created, which uses the mustache templating system with variable placeholders {{network}} and {{address}}. To deploy the subgraph for mainnet or Rinkeby (local/dev) simply run one of the following commands:
# Mainnet:
yarn prepare:mainnet && graph deploy --node https://api.thegraph.com/deploy/ --ipfs https://api.thegraph.com/ipfs/ <SUBGRAPH_ACCOUNT>/<SUBGRAPH_NAME>
# Rinkeby (localhost):
yarn prepare:local && graph deploy --node https://api.thegraph.com/deploy/ --ipfs https://api.thegraph.com/ipfs/ <SUBGRAPH_ACCOUNT>/<SUBGRAPH_NAME>
# Rinkeby (develop):
yarn prepare:rinkeby && graph deploy --node https://api.thegraph.com/deploy/ --ipfs https://api.thegraph.com/ipfs/ <SUBGRAPH_ACCOUNT>/<SUBGRAPH_NAME>
Example subgraph account and name: sophiacodes/the-lao-localhost
Any changes to mapping.ts, schema.ts or schema.graphql will require a rebuild, use yarn build. Then prepare and deploy using one of the above yarn commands.
See here for more information
If a new subgraph has been deployed under a different account for either testnet or mainnet, the new subgraph URI will need to be updated in the org table in the LAO database. There are two columns, one for testnet graphURLTestnet and the other for mainnet graphURLMainnet.