v0.3.0

Author: nman98

.github/workflows/release.yml

@@ -66,14 +66,14 @@ jobs:
             You will need to set up the database for the indexer, check the docs for more information.
             When you have the database running run the cmd to create the database and the user.
             ```bash
-            go run cmd/setup.go create-db --db-host localhost --db-port 5432 --db-user postgres --db-name postgres --ssl-mode disable --new-db-name gnoland --chain-name gnoland
-            go run cmd/setup.go create-user --db-host localhost --db-port 5432 --db-user postgres --db-name postgres --ssl-mode disable --user writer --privilege writer
+            indexer setup create-db --db-host localhost --db-port 5432 --db-user postgres --db-name postgres --ssl-mode disable --new-db-name gnoland --chain-name gnoland
+            indexer setup create-user --db-host localhost --db-port 5432 --db-user postgres --db-name postgres --ssl-mode disable --user writer --privilege writer
             ```
 
             From here you can run the indexer using live or historic mode
             ```bash
-            ./indexer live --config config.yml
-            ./indexer historic --config config.yml --from-height 1000 --to-height 2000
+            ./indexer run live --config config.yml
+            ./indexer run historic --config config.yml --from-height 1000 --to-height 2000
             ```
 
             For more information check the docs.

CHANGELOG.md

@@ -5,6 +5,23 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.3.0] - 2025-11-10
+
+In this release there are some fixes and improvements. The live process should work properly now and the REST API has some new routes. CLI commands are now combined with the ones from the setup cli. Some processes have been improved to use less memory. 
+
+### Added
+
+- The REST API has some new routes. The API can now return last block height, last number(x) of blocks, last x transactions. [789c24b](https://github.com/Cogwheel-Validator/spectra-gnoland-indexer/commit/789c24b18881cd33758677f8b878aff7bb42f9dc)
+
+### Changed
+
+- The CLI commands are now combined all together so the cmd/setup.go is removed and the users can now only download the main cli and initiate everything they needs for the indexer to work. [805513b](https://github.com/Cogwheel-Validator/spectra-gnoland-indexer/commit/805513b20fdd4f452e8d6f5ad6d56d318e78d5d9)
+- Changed the data and query operators to use mutex and store any data they process/collect directly into the type they need to return. There shouldn't be any major preformance difference but it should alocate less memory. [89e5b6d](https://github.com/Cogwheel-Validator/spectra-gnoland-indexer/commit/89e5b6d103710970cbe69c02865bb4b0727649b3)
+
+### Fixed
+
+- When Indexer started to run in live mode without any previous data it should start tho prcess the data from frist block height. But instead it tried to query block height 0. [3517e5a](https://github.com/Cogwheel-Validator/spectra-gnoland-indexer/commit/3517e5aec32a21d70f43b0595d842841098a4c47)
+
 ## [0.2.1] - 2025-10-06
 
 Not really much of a change just added dockerignore file, small changes to the release.yml so it pushes the api also.

docs/setup.md

@@ -42,31 +42,32 @@ The important thing to setup is the database connections. The indexer can do goo
 However if you are planning to add a lot of services a top of the database maybe increase it. The docker compose is 
 set to 500 connections.
 
-For creating all of the necessary tables and types you can use the setup.go file in the cmd directory.
-The cmd has two commands to create the database and the user:
+For creating all of the necessary tables and types you can use the indexer executable and the setup command.
+The cmd has 3 commands to create the database and the user:
 
 ```bash
- collection of tools to set up and manage the database for the gnoland indexer.
+A collection of tools to set up and manage the database for the gnoland indexer.
 
 Usage:
-  setup [command]
+  indexer setup [command]
 
 Available Commands:
-  completion  Generate the autocompletion script for the specified shell
-  create-db   Create a new database named gnoland
-  create-user Create a new user for the database
-  help        Help about any command
+  create-config Generate a config with default values.
+  create-db     Create a new database named gnoland
+  create-user   Create a new user for the database
 
 Flags:
   -h, --help   help for setup
+
+
 ```
 
 To use all of these commands you will need a user with admin privileges.
 In the example below the user is postgres you will be asked for the password.
 To create the database you can use the following command:
 
 ```bash
-go run cmd/setup.go create-db --db-host localhost --db-port 5432 --db-user postgres --db-name postgres --ssl-mode disable --new-db-name gnoland --chain-name gnoland
+indexer setup create-db --db-host localhost --db-port 5432 --db-user postgres --db-name postgres --ssl-mode disable --new-db-name gnoland --chain-name gnoland
 ```
 
 To create the users for the database you can use the following command. 
@@ -76,7 +77,7 @@ The privilege level can be "reader" or "writer". The reader should have only the
 The writer should have the select, insert, update and privileges.
 
 ```bash
-go run cmd/setup.go create-user --db-host localhost --db-port 5432 --db-user postgres --db-name postgres --ssl-mode disable --user writer --privilege writer
+indexer setup create-user --db-host localhost --db-port 5432 --db-user postgres --db-name postgres --ssl-mode disable --user writer --privilege writer
 ```
 
 ## Running the indexer
@@ -86,25 +87,23 @@ The indexer can be ran in 2 modes: live and historic.
 Now when you have the database running you can actually run the indexer. The indexer has a lot of flags that can be used to configure it:
 
 ```bash
-A blockchain indexer for Gnoland that processes blocks and transactions.
+Run the indexer in either live or historic mode.
 
 Usage:
-  indexer [command]
+  indexer run [command]
 
 Available Commands:
-  completion  Generate the autocompletion script for the specified shell
-  help        Help about any command
   historic    Run the indexer in historic mode
   live        Run the indexer in live mode
 
 Flags:
   -e, --compress-events              compress events
   -c, --config string                config file path (default "config.yml")
-  -h, --help                         help for indexer
+  -h, --help                         help for run
   -m, --max-req-per-window int       max requests per window (default 10000000)
   -r, --rate-limit-window duration   rate limit window (default 1m0s)
   -t, --timeout duration             timeout (default 20s)
-  -v, --version                      version for indexer
+
 ```
 
 Compress events doesn't work at the moment so do not use it! 
@@ -114,6 +113,14 @@ The max request per window is rated to the max request that can be made to the R
 The timeout is the timeout for the RPC requests. The default is 20 seconds. You can set it to lower if you want.
 
 The config file is needed to configure the indexer. You can use the config.yml.example file as a template.
+Or use the create-config command to create a config file with default values.
+
+```bash
+indexer setup create-config --config config.yml
+```
+
+The config file is a YAML file that contains the configuration for the indexer.
+
 ```yaml
 # Example config file for the indexer
 
@@ -169,7 +176,7 @@ exponential_backoff: 2s
 
 To run the indexer in historic mode you can use the following command:
 ```bash
-indexer historic --config config.yml --from-height 1000 --to-height 2000
+indexer run historic --config config.yml --from-height 1000 --to-height 2000
 ```
 The from height is the starting height of the block to index. The to height is the ending height of the block to index.
 The indexer will index the blocks from the from height to the to height inclusive. You can also add the other flags
@@ -185,7 +192,7 @@ It can also be useful if you want to index blockchain partially and work with da
 or partial scan of the chain where you want to index from a certain height to a certain height.
 
 Usage:
-  indexer historic [flags]
+  indexer run historic [flags]
 
 Flags:
   -f, --from-height uint   starting block height (default 1)
@@ -202,7 +209,7 @@ Global Flags:
 
 To run the indexer in live mode you can use the following command:
 ```bash
-indexer live --config config.yml
+indexer run live --config config.yml
 ```
 Live mode flags:
 ```bash
@@ -214,7 +221,7 @@ However if you do not need previous data, you can run the live mode with the ski
 Afterwards you can run live mode normal without the skip-db-check flag.
 
 Usage:
-  indexer live [flags]
+  indexer run live [flags]
 
 Flags:
   -h, --help            help for live
@@ -258,16 +265,16 @@ Like mentioned above you can use the docker-compose.yml file to setup the databa
 If you plan to run the indexer over docker you can use this commands:
 ```bash
 # Live mode with custom config
-docker run gnoland-indexer live --config /path/to/config.yml --skip-db-check
+docker run gnoland-indexer run live --config /path/to/config.yml --skip-db-check
 
 # Historic mode
-docker run gnoland-indexer historic --from-height 1000 --to-height 2000
+docker run gnoland-indexer run historic --from-height 1000 --to-height 2000
 
 # Show all available commands
 docker run gnoland-indexer --help
 
 # Show help for specific command
-docker run gnoland-indexer live --help
+docker run gnoland-indexer run live --help
 ```
 
 You can also run the indexer with something like systemd:
@@ -277,7 +284,7 @@ Description=Gnoland Indexer
 After=network.target
 
 [Service]
-ExecStart=/path/to/indexer live --config /path/to/config.yml
+ExecStart=/path/to/indexer run live --config /path/to/config.yml
 Restart=always
 RestartSec=5
 User=$USER