Fix/online events

[ramonaspence]

The online events were not coming in because of the way they were being formatted into the event dictionary on lines 223 - 237. So I just made an it an if else statement, allowing the events with no venue_id be added to the dictionary.

The name of the days_in_the_past has been changed in the config.ini.example

[ramonaspence]

I started to fix the block of code that defaults the start_date of the query to today so that it defaults to days_in_the_past

In the process, Flask is giving me a lot of small little errors (keyerrors, typeerrors) to work out before being able to debug further.

When I run the Flask app, I'm getting a consistent 500 response code, but I believe this only requires some refactoring of the app.

[ramonaspence]

I've also fixed a couple of small TypeErrors that Flask did not like. The app now runs on a local server with status 200.

[allella]

Cool. Squashed and merged this into this "upstream" master branch. That's the branch the production website is "tracking" so when I do a get pull on the master branch of the production site it will get this commit.

[allella]

[allella]

If you check out your local .git/config file you'll see the git mappings for origin and any "upstreams" you added.

In this case, I added a bcsnipes "upstream" when @bcsnipes was helping out, which allowed me to checkout a copy of his fork to test something and then switch back to the local master branch when I was done.

[ramonaspence]

Neat! I'm starting to get the hang of it/ a good grasp on it!
I like the idea of making different/new branches for certain fixes then deleting them when the fix is complete/merged as suggested in the Chapter repo you sent me.

Although naming things clearly is vital and somehow really difficult lol!