Currently the graphs for these contracts are deployed by connecting on our own graph server via SSH, then adjusting the config files manually depending on which chain to use. It would be nice to have a system where the contracts for the different chains are managed in config files and then when running an npm command, one can choose from a prompt which chain to deploy. A fully automatic pipeline is not required yet.
On each chain the graph should have a unique name. Maybe the chain name can automatically be added to the graph name or so. The frontend will then just fetch the graphs by name (already implemented).
Currently the graphs for these contracts are deployed by connecting on our own graph server via SSH, then adjusting the config files manually depending on which chain to use. It would be nice to have a system where the contracts for the different chains are managed in config files and then when running an npm command, one can choose from a prompt which chain to deploy. A fully automatic pipeline is not required yet.