Update database to work with Oauth

[ryantanaka]

@jygh98, can you meet this Thursday 3:00pm so we can update the database on the server to work with Oauth? Once we pull your merged changes onto the server, we can make sure all the functionalities are working properly and get #40, #33, #31, #29, #23, #7 closed on the issues list.

[jygh98]

@ryantanaka 👍

[carlosparadis]

As discussed today with @jygh98 , my understanding is that a new table oauth was created. But the current status of the user and users table which is no longer used by survey_admin (or any other app on the server), remains. Can someone confirm? I would like to keep dead code and tables to a minimum to avoid ambiguity and confusion down the road.

[ryantanaka]

@ryantanaka

note 3/2/18:

Still need to do #40, #33, #31, #29

[ryantanaka]

@carlosparadis, You are right about the oauth table. I confirmed that users is not needed. I will go ahead and remove it from the database.

@jygh98, hey jason, am i missing something? i can't seem to find code referencing to the is_deployed column of the deployed_url table or any type of feature associated to #40 when running the web app locally. is #40 done or do I need to code that up? LMK, thanks

[ryantanaka]

@jygh98, actually nvm I see the code on your fork 33-allow-to-edit-survey-admin.

[jygh98]

@ryantanaka 👍

[ryantanaka]

the database is set up with the oauth table (both jason and I are added at the moment), I am closing this issue