Node-RED

by nervecentergarage

GitHub Readme.md

Access to heroku app :

https://auto-nrv-cntr.herokuapp.com/

Overview

It takes a village to do structured journalism. Coordinating among so many disparate activities is a serious barrier. We believe that, if done right, smart automation tools can help. This team will attempt to use intelligent automation to coordinate developer activity, content production, and content presentation into a working structured journalism ecosystem.

Key Team Skills

Collectively, the team must have the following skill:

  1. Finite-state machines
  2. Flask
  3. Node Red
  4. JavaScript
  5. JSON
  6. MongoDB
  7. Docker
  8. Azure

Roles and Responsibilities

  1. (3) Community simulation developers-- Use Flask to create finite-state machine simulations of content developers, expert communities, and fact checkers. Publish APIs for the simulations. Read from and write to the MongoDB content repository.
  2. (1) MongoDB repository and content developer-- Create a content repository in MongoDB. Populate it with JSON data that the community simulators need to run their simulations.
  3. (1) Node-Red flow developer-- Use Node-Red to coordinate across the community simulations.
  4. (1) Node-Red dashboard developer-- Use Node-Red to create a dashboard that provides a summary of what is happening in the Node-Red flows.
  5. (1) Platform engineer-- Package Node-Red and community simulations into a Docker container. Publish and run the container in Azure.

Codes in progress (Details can be found in "Code --> Finite State Machine" folder)

  1. FSM Editor

  2. FSM Journalist

  3. FSM Publisher

Workflow in progress (Details can be found in "Code --> Node-red" folder)

  1. Assignment workflow
  2. FSM Workflow

Database connection (Details in "Code --> Database" folder)

Deployment

  1. Manual deployment in progress.