Separating dev & prod. settings

- secret key is imported from os.eviron
- debug flags are toggled off in production
Adding toronto_fire to INSTALLED_APPS
Incident Model

First iteration of our incident model

- incident_number as the primary key
- fields to track start, arrival and end time, and the incident's
type, alarm level, and number of trucks/units dispatched
Setting up migrations
Model Unit Tests

- First unit test for Incident Model
Incident Model Schema Change

- start, arrival and end times are stored as DateTimeFields
- schema migration for the field changes
use datetime module to properly create Incident times in IncidentTestCase
Import Incidents Command scaffolding

django command that will accept a csv file, parse and import
incidents into the database
import_incidents Command Unit Test

- creates a single row csv file to test import_incidents
command unit test should write a header row to unittest.csv
Implementing import_incidents command

- parses out incident number, start/end times, alarm level and number of units
- missing columns in unittest, and test passes now
Fixing date format, csv doesn't use AM/PM and uses 24-hr
Incident View and Template

- putting all templates into toronto_fire/templates
- setting Incident view as the root view
- view queries for avg number of units per incident type
- loading d3 via CDN service for now
Bar Chart with avg number of trucks using D3
Correcting bar graph rendering

- scale for bars was incorrect
- added stroke styling to bars
Duration function for Incident Model

- created get_duration() function, which returns the length of the incident in seconds
- added unit test
Incident Model duration field

- adding a field to Incident to track it's duration
- updated import script and migrations
Initial Scatterplot graph to compare # of trucks and avg duration
fixed scatter plot with the correct properties and changing y-axis to a logarithmic scale
import csv data to Heroku