geo-points-svc

Description

Core service of Points System for Georgia local usage

Install

git clone github.com/rarimo/geo-points-svc
cd geo-points-svc
go build main.go
export KV_VIPER_FILE=./config.yaml
./main migrate up
./main run service

API documentation

Online docs are available.

All endpoints from docs MUST be publicly accessible.

Private endpoints

Private endpoints are not documented and MUST only be accessible within the internal network. They do not require authorization in order to simplify back-end interactions with Points service.

The path for internal endpoints is /integrations/geo-points-svc/v1/private/*.

Add referrals

Private endpoint to set usage count for genesis referral code or create a new System user with genesis referral code. System user is unable to claim events or withdraw, it has is_disabled attribute set to true, so the client app should not allow it interactions with the system, although it is technically possible to do other actions.

Path: /integrations/geo-points-svc/v1/private/referrals Body:

{
    "nullifier": "0x0000000000000000000000000000000000000000000000000000000000000000",
    "count": 2,
    "infinity": true
}

Response:

{
  "referral": "kPRQYQUcWzW",
  "usage_left": 2,
  "infinity": true
}

Parameters:

• nullifier - nullifier to create or edit referrals for
• count - number of referral usage
• infinity - specify if referrals code have unlimited usage count

Local build

We do use openapi:json standard for API. We use swagger for documenting our API.

To open online documentation, go to swagger editor here is how you can start it

  cd docs
  npm install
  npm run start

To build documentation use npm run build command, that will create open-api documentation in web_deploy folder.

To generate resources for Go models run ./generate.sh script in root folder. use ./generate.sh --help to see all available options.

Note: if you are using Gitlab for building project docs/spec/paths folder must not be empty, otherwise only Build and Publish job will be passed.

Running from Source

• Run dependencies, based on config example
• Set up environment value with config file path KV_VIPER_FILE=./config.yaml
• Provide valid config file
• Launch the service with migrate up command to create database schema
• Launch the service with run service command

Database

For services, we do use PostgresSQL database. You can install it locally or use docker image.