Run the indexer as its own process and docker-compose service - #713
Merged
Akatenvictor merged 3 commits intoSep 29, 2026
Merged
Akatenvictor merged 3 commits into
Akatenvictor merged 3 commits into
Conversation
- npm run indexer alias (same entrypoint as worker:indexer), so it matches the SongProcessorWorker's npm run worker pattern - indexer docker-compose service reusing the app image, wired to the same Postgres/Redis, with its own healthcheck - README Scripts table entry AudioBitsStellar#231 (indexer ADR) and AudioBitsStellar#232 (cursor persistence) are already done on main: docs/adrs/010-indexer-architecture.md covers all 5 contracts and the polling/cursor design, and src/entities/IndexerCursor.ts + migration already implement per-contract/per-network cursor persistence. Left comments on those issues rather than duplicating. Closes AudioBitsStellar#245 Closes AudioBitsStellar#246
|
@ANTIDOT20 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
Author
IndexerCursor already tracked lastProcessedLedger per contract+network, but issue AudioBitsStellar#232 also asks for the last processed event ID so a restart resumes after the exact event, not just re-polls the whole ledger it was in. Adds lastProcessedEventId (nullable varchar) to the entity, a migration, and threads it through IndexerService.recordProgress/ getStatus/getAllStatus. Closes AudioBitsStellar#232
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #245
Closes #246
Closes #232
npm run indexeralias (same entrypoint asworker:indexer), matching theSongProcessorWorker'snpm run workernamingindexerdocker-compose service reusing the app image, wired to the same Postgres/Redis, with its own healthcheckIndexerCursoralready persistedlastProcessedLedgerper contract+network, but the issue also asks for the last processed event ID so a restart resumes after the exact event rather than re-polling the whole ledger. AddedlastProcessedEventId(nullable) to the entity + a migration, and threaded it throughIndexerService.recordProgress/getStatus/getAllStatus.#231 (indexer ADR) is also already done on
main(docs/adrs/010-indexer-architecture.md) but isn't assigned yet, so it's left out of this PR.