ci: add indexing node for dex-explorer #3825
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We're starting work on a new webapp that will provide a visual frontend for the DEX. That work is currently housed in [0]. Similar to cuiloa [1], we must enable CometBFT indexing to Postgres, so the application (yet to be written) can query those events. Strictly speaking, it's possible to reuse a db connection across multiple apps, particularly if we're careful about ensuring read-only access, but duplicating the node config per-app will simplify debugging in the near-term.
These changes have been manually applied for both environments. URLs may change in the future.
[0] https://github.com/penumbra-zone/dex-explorer
[1] https://github.com/penumbra-zone/cuiloa