Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback, Suggestions and Questions #4

Open
pete-eiger opened this issue Jul 18, 2023 · 1 comment
Open

Feedback, Suggestions and Questions #4

pete-eiger opened this issue Jul 18, 2023 · 1 comment
Labels
type:tracking Tracking issues with related scope

Comments

@pete-eiger
Copy link
Contributor

Please share your feedback, feature suggestions, questions, and everything in between

@pete-eiger pete-eiger pinned this issue Jul 18, 2023
@hopeyen hopeyen unpinned this issue Jul 18, 2023
@hopeyen
Copy link
Collaborator

hopeyen commented Jul 19, 2023

From Discord discussions, we can consider these suggestions

  1. Update docs to show how to add the GraphQL plugin and datasource, dashboard provisioning, update RUST_LOG env vars (potentially a brief expectations of what to expect in start-up logs
  2. Submit a PR to the StakeSquid repo to use the operator key by default and use id_validation to indexer, so it just works out of the box. (I think this has been worked on
  3. indexers who runs an IPFS node could communicate the pinned manifest files rather than relying on the E&N ipfs node. (It is better to simply integrate in the indexer-service server with route to /ipfs for peer info or the IPFS node API with limitations.

Did not receive any interest in Deployment health, indexing status, cost model (should've asked for warp sync and metrics

@pete-eiger pete-eiger added the type:tracking Tracking issues with related scope label Aug 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:tracking Tracking issues with related scope
Projects
None yet
Development

No branches or pull requests

2 participants