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

Updating readme for postgres 13 and AZ note #810

Merged
merged 3 commits into from
Dec 17, 2021
Merged

Updating readme for postgres 13 and AZ note #810

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
33885f3
Update README.md
algojack Dec 17, 2021
abf1c0f
Update README.md
algojack Dec 17, 2021
d4ca3ea
Update README.md
algojack Dec 17, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,10 @@

The Indexer is a standalone service that reads committed blocks from the Algorand blockchain and maintains a database of transactions and accounts that are searchable and indexed.

# Minimum Version Requirements
# Tested Requirements Versions

* [go 1.16](https://golang.org/dl/)
* [Postgres 11](https://www.postgresql.org/download/)
* [Postgres 13](https://www.postgresql.org/download/)

# Quickstart

Expand Down Expand Up @@ -78,6 +78,8 @@ There are two primary modes of operation:
### Database updater
In this mode, the database will be populated with data fetched from an [Algorand archival node](https://developer.algorand.org/docs/run-a-node/setup/types/#archival-mode). Because every block must be fetched to bootstrap the database, the initial import for a ledger with a long history will take a while. If the daemon is terminated, it will resume processing wherever it left off.

Keeping the indexer daemon as close as possible to the database helps minimize latency. For example, if using AWS EC2 and RDS, we suggest putting EC2 in the same VPC, Region, and even Availability Zone.

You should use a process manager, like systemd, to ensure the daemon is always running. Indexer will continue to update the database as new blocks are created.

To start indexer as a daemon in update mode, provide the required fields:
Expand Down