Twitteranddb

[twinlensreflex]

I have:

• added an extra html template and route (mentorlist.html and /mentor) to test populating Flask/Jinja2 from the database (successfully 👍 )
• split/refactored (and subsequently removed) datamodels.py, resulting in:
  • cordb.py where the database is instantiated
  • flask_data_models.py where the classes for the db tables and their relationships are defined
  • app.py which calls cordb and the classes in order to connect to the database with db.init_app(app)
• added a twitter directory where you can find
  • add_to_db.py containing all the functions you might need to call to add to the db (taking a list as an argument and looping + adding for each list item)
  • dbconnect.py where you can connect to the database without Flask
  • tweetparse.py which contains an example tweet and functions to split it into manageable and related chunks
  • twitterstream.py which will open a stream to the twitter api and track the specific hashtag

[twinlensreflex]

(accidentally closed this while trying to add more comments.. whoops!)

[madeleinel]

It looks really good! I've looked through it tonight, look forward to testing it all out myself (hopefully tomorrow)

---

Just a couple of quick questions before I merge it:

• Do you want to keep the temporary @app.route("/mentors”) (within app.py) & mentorlist.html for testing? Or should we remove that?
• What does “idx” (in twitter/add_todb.py) refer to? I couldn't find it defined anywhere outside of the "for idx, skill in enumerate(skillist):..."_ functions so a bit unclear on that one

---

Also, don't forget to send me the real config.cfg file :) ( & I'll send you the Twitter app keys for WomenToTech )

[twinlensreflex]

Sure

• We'll need a /mentors and /mentees route anyway, right? so maybe let's keep it?
• ahh, it's index, enumerate() is a built in function which returns the indices of a list in a 'for in' loop

you shouldn't need the actual config file, you can just hook it up to a local db, none of that stuff will be used when we deploy it anyway because the info will be for heroku postgres (probably...) but if you do want to use the same ones i accidentally left the connection info in for the twitter db connection 👀 but yeah if you just create a db locally and use the info you used to create it to connect (postgres username, password, port, dbname)