Big Brother Dev Setup

• cd student-monitor
• npm install
• sudo npm link - This is necessary to make sure that its available as a global command
• cd to/a/valid/github/repo
• bigbrother - This can be changed at big-brother/package.json:bin

Master Server Setup

• Ensure you have mongodb installed
• Start mongodb on port 27017 - this can be changed at master-server/config/default-config:db.url (Will likely change be changed to getconfig or another npm module)
• npm start

Logging in

• By default there are two users created, you can see these users in the terminal of the master-server
• student{name:"stu",pass:"A random password"}
• ta{name:"ta",pass:"A random password"}
• goto "/login" or "/" (which will redirect to "/login")
• fill out the form with either student or ta
• it will redirect to "/" which will serve either the student or ta portal

What Is working:

• Master server start
• logging in
• Minimal UI
• Big brother starts
• Big brother sends diffs on filesystem change
• Big brother sends diffs on commit
• Big brother sends tarball on request
• Big brother can be stopped
• Big brother runs in the background
• Master Server Recieves and Stors Diffs, Tars, commits and filesystem changes
• Master server updates TAs on commit and filesystem changes
• Tas Update the graphs

Known issues

• Big brother sends fs add events on start
• Busboy hangs when a file is empty or invalid No longer using busboy
• Some ui is working
• Streaming on the Browser is near impossible currently without creating our own wrapper
• SuperAgent and Request Both do not work within webworkers
• Formdiable Hangs (sometimes) form some reason - Switched to Multiparty to avoid issues, hard to reproduce without showing full code
• Flow and Subchart Apis don't mix and match c3js/c3#383

Known Refactoring necessary

• Abstract/mongooseRouter - remove anonymous functions, create a context object
• Abstract/mongooseRouter#17 - Expensive operation for the sake of pretty urls
• Abstract/mongooseRouter#123 - Peice out use cases
• /Models/ - Permissions should not be with the model
• During Server Starts, we want to ensure all ta's are considered not online -When moving to production, we want to ensure this happens whenever the ws server starts -Current place is in master-server/debug.js
• Need to add any "waiting" help requests to the escalation queue if the server restarts
• Need to ensure that we know the semester so we can limit our searches each time

Known Necessities

• Seperate Students and TAs By classroom
  • Send Help requests locally first, then globally
• Seperate All users by "semester" (I forget the vocabulary)
  • Otherwise, may include students/Tas that have been fired or more
• Access the users that have paid
• Connecting P2P during help request

Long Term Enhancements

• For student-monitor
  • Display Passes and Failures in graph
  • Display full information in regards to a specific peice of information
  • Allow the TA to set things to listen for - File deletes, etc
• for Help request
  • When a diff is triggered for a particular file - live update the snapshot
  • When a diff is triggered for a particular file - send the diff to tas looking at them
• Can do an abstract data to view binding with certian lists -HelpRequest List -Student List for fraphs

What should be working but likely is not

• Should be able to send post requests with "files" to master server, these files will be saved into gridfs
• Should be able to retrieve files from master server
• Should be able to parse the files retrieved from master server on client -gitParse -tar-parse-To display snapshots of help requests

Relevent issues

• mscdex/busboy#73
• mscdex/dicer#2
• ladjs/superagent#455 (comment)
• ladjs/superagent#546
• https://github.com/substack/node-git-emit/pull/4
• form-data/form-data#108
• pillarjs/multiparty#108
• request/request#1589
• ladjs/superagent#659
• http://www.bennadel.com/blog/2817-the-affect-of-back-pressure-when-piping-data-into-multiple-writable-streams-in-node-js.htm