GitLab

Start and stop threads when clients are created or removed
Watchdog watches for changes to the ./data/clients.json
When a change is detected it compares the list of running
clients to the content of clients.json and starts or
stops client processing threads as required

Gitlab-ci

Closes #20

See merge request !8

feat: suppressing pycache generation

feat: added in test compose and changed compose script to allow more options

Resolve "Unit tests for HTTP API endpoints"

Closes #23

See merge request !11

+ fix to max_messages query string handling

- done
  - client and token model
  - client and token api endpoints
  - send api endpoint
- todo
  - notify api endpoint
  - receive api endpoint

Resolve "Create a docker-compose to run RMQ, the bus and the API"

Closes #17 and #13

See merge request !7

fix: added shebang to run-compose
refactor: DATA_DIR used in container as well as external to it

refactor: MQ_HOST default in run-compose script

Resolve "Fix client post API endpoint"

Closes #22

See merge request !10

feat: added docker-compose setup, inc run-compose and .env to handle vars for locally running
refactor: changed rmq to fail when it can't connect, allowing stuff to wait until the MQ is available
refactor: moved from assuming pipenv to just pip
refactor: mounted volumes, so changed interactions with clients.json to match

Wrapping rmq

Closes #16 and #7

See merge request !5

refactor: use subscribe as Q to xchange binder

refactor: deleted hello.py
fix: minor comment typo

prototype soar backbone implementation

Closes #1

See merge request !3

refactor: spot of tidying up notes
fix: subscribe wasnt handling closing connections