Content Curation Web App for Disaster Volunteers
Want to help out? First check out our wiki to set up your workstation.
How to Run Our Code
You'll need to start up both Chrome and our Server/DB
- Chrome: Linux:
open /Applications/Google\ Chrome.app --args --disable-web-security
- Server & DB:
./startTo restart use
Flags available in start script:
-mStarts only mongo server daemon
-hRuns only historicTweets.py and processes it depends on.
-cRuns only crisisServer.py and processes it depends on.
-iReserved. Will be used to do initialization stuff.
- Behavior when no flags are mentioned: All 3 processes are started. Similar to
Flags available in stop script:
-mStops mongo server daemon and all processes that depend on it.
-hStops only historicTweets.py.
-cStops only crisisServer.py.
- Behavior when no flags are mentioned: Stops all processes except the mongo server daemon. Similar to
If things aren't working you can do things manually here.
Resetting Historical Tweet Stream
You'll know you've run out of tweets once you see this one pop up:
"Ottawa overrules health officials on heroin replacement study - OTTAWA &" from wwwHUMORcat or "RT @TornadoTitans: “@yaya_castillo: This pipeline explosion is 50+ miles east between Forgan &" from Leonisx
At this point, you need to restart the historical tweet stream. This can be accomplished by:
- Opening the DB Shell [see above]
- Type in:
use current_databaseand press enter
- Type in:
db.tweets.drop()and press enter.
- You should see
trueoutputted back to you.
- Stop the historical tweet stream [see above] by typing
Ctrl-Cand then starting it up again.