Cardano GraphQL API Local Deployment Issues - Failure in Applying Hasura Metadata

[PardusEidolon]

Ask a question

I am currently facing an issue while deploying the Cardano GraphQL API locally on the preprod testnet, without Docker. The issue arises during the application of Hasura metadata by the cardano-graphql-background server.

My environment variable METADATA_SERVER_URI is set to https://tokens.cardano.org, which is presumably the intended metadata server. However, this URI appears to just lead to an Nginx server with no clear metadata path that the cardano-graphql-background process could use.

Despite these issues, health checks seem to return positive results, suggesting that the server is operational to some extent.

This problem is particularly impacting the functionality of cardano-ql and cardano-ql-background, given their interdependencies.

One part of this situation that confuses me is the exact role of https://tokens.cardano.org. The current documentation does not appear to explain the purpose of this resource in this context.

Is there any workaround or alternative approach that would allow me to bypass these issues and successfully deploy the Cardano GraphQL API locally? Any guidance or clarification would be greatly appreciated.

[Kartiiyer12]

@PardusEidolon For preprod testnet, can try setting the METADATA_SERVER_URI to - http://metadata.world.dev.cardano.org and if its able to pick the asset metadata.