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.

Sign up for GitHub

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

Jump to bottom

Add an option to disable the indexer #84

Open
ptrus opened this issue Nov 30, 2021 · 1 comment · May be fixed by #284
Open

Add an option to disable the indexer #84

ptrus opened this issue Nov 30, 2021 · 1 comment · May be fixed by #284
Labels
p:2 Priority: desired feature

Comments

@ptrus
Copy link
Member

ptrus commented Nov 30, 2021

That wold enable having multiple instances of web3 deployed using the same DB where one would be used as the indexer, and other would be used for serving queries (only need read-only access to the DB).
@ptrus ptrus added the p:2 Priority: desired feature label Nov 30, 2021
@ptrus
Copy link
Member Author

ptrus commented Jan 11, 2022

This would also require changing the event system, as events are sent directly from the indexer https://github.com/oasisprotocol/emerald-web3-gateway/blob/50a5aefa81c2f9f8f3e5b2c4f8e0cec98d896ea2/indexer/utils.go#L291-L297

@Yawning Yawning mentioned this issue Mar 28, 2022
Closed
This was referenced May 25, 2022
Closed
Merged
@Yawning Yawning linked a pull request Jun 8, 2022 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
p:2 Priority: desired feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Add a way to follow a SQL db instead of indexing oasisprotocol/oasis-web3-gateway
1 participant
@ptrus