Incoming queries - sigurdga/Smart113 GitHub Wiki

Operating personnel should not have to search manually or reload a page to see incoming user information from our database.

Or database and Django on top of it has all information we need, but the django cannot easily update the operating personnel's screens.

We assume they have a browser open, as we cannot open a browser on their system.

Incoming requests are coming automatically from "external system". This is the way a request goes from "external system" to "appearing on operators screen" in an (internal only) incoming result screen:

• "external system" writes incoming phone number to…
• trigger a Django management command that will query the database and push results to…
• socketio a small nodejs service that will push results to all browsers having the internal result page up

To get this going, we have a setup of:

• varnish: for caching web request and routing traffic to conventional web server or nodejs process
• conventional web server: apache or nginx
• django running in apache or by gunicorn through nginx
• nodejs/socketio simple push service

The varnish routing is not needed in production environment, as the push service will only run internally.