0.1.0 • Published 4 years ago

gp-pos v0.1.0

Weekly downloads
-
License
MIT
Repository
-
Last release
4 years ago

see gp-pos-docs.docx for details

Test

  • via GET Requests (where 5000 is .env WEB_BRIDGE_PORT)

Collection Controll Service Tests Endpoints

(usually controlled by cron jobs)

The collection_control db is the only one which remains constant. It only every has one document in it. The document with id: 0. This document tells the rest of the application what the database names are that are currently in use.

env.json setting "ENTITY_COLLECTION_DISK_SIZE_LIMIT": 500, this is the limit of either a single dbs for all others (not the sales-order-open_xxxx), and in the case of sales orders what all the shift disk sizes can add up to.

db disk sizes can be seen on http://localhost:5984/_utils/ The number is size in mb for testing you can change it to be really small eg : 0.200 is 200kb the customers db is usually 428.3 KB which means running prim-job-c-other will result in a new customers db being created

These 2 are usually executed by scheduled job:

  1. http://localhost:5000/test/prim-job-new-shift create new shift sales-orders-open_xxxx and update collection_control doc id: 0

  2. http://localhost:5000/test/prim-job-c-other will create new other (than sales-orders) dbs if they are above a certain disk size

These nest 2 are executed on till on startup and will clean out old not active dbs according to the following rules

  1. http://localhost:5000/test/job-d-sos will add up the disk sizes of all the sales-order-open_ dbs and then delete any the sum to above 2/3 of the limit from the oldest first

  2. http://localhost:5000/test/job-d-other will just delete any other dbs no longer referenced in the collection_control db

Dev Admin

  • via GET Requests (where 5000 is .env WEB_BRIDGE_PORT)

http://localhost:5000/dev-admin/refresh-fe http://localhost:5000/dev-admin/init-all

http://localhost:5000/dev-admin/reset staging, production http://localhost:5000/dev-admin/restart staging, production http://localhost:5000/dev-admin/clear-logs staging, production

Notes

on linux had to install libudev-dev to make usb 1.5.0 dep of escpos-print-extended build

"MAX_LAST_UNITY_CHANGES": 3, (hours)

Change to package local file for shared in dev

"dependencies": { "@gaap/gp-pos-shared-models": "file:../gp-pos-ui/dist/gp-pos-shared-models" }

Change package to plubished version for cloud build (tb = temp branch)

"dependencies": { "@gaap/gp-pos-shared-models": "0.1.3" }

Unity Internal IP Addresses

"INIT_UNITY_API_URL": "http://10.50.200.251:1120/",
"INIT_UNITY_BROKER_URL": "mqtt://10.50.200.251:1121/",

"INIT_UNITY_API_URL": "http://localhost:8000/",
"INIT_UNITY_BROKER_URL": "mqtt://localhost:1883/",

"INIT_UNITY_API_URL": "http://unity.gppos.net:8762/",
"INIT_UNITY_BROKER_URL": "mqtt://unity.gppos.net:8862/",

Production timeout

"MAX_LAST_UNITY_CHANGES": 3000000000,