GEOGRAPICS

• Backend uses Node.js with Express, and an SQLite3 server. Heroku plugin used on hosting site to convert the database to PostGres

• Users come to the site and are routed through Instagram's verification/login process, using passport. Once verified, Instagram sends the user's data to the database

• Two tables have been created - users and pictures

  • Users table stores users who have passed through the Passport/Instagram authentication process
  • Pictures table stores their data from Instagram once they've authorized the Geograpics app in their Instagram file

• Partial/As-Needed CRUD functionality has been created at two endpoints/routers

  • /users and /map
  • /users has been commented out - currently unused, but useful for future releases
  • functions for user router are found in userHelper.js, functions for picture router are found in pictureHelper.js
  • Both endpoints are behind a token checking authentication file.

• User Router functions (currently commented out due to non-use):

  • POST at "/users": insert new user into db
  • PUT at "/:id" - edit existing user info
  • DELETE at "/:id" - delete user

• Picture Router Functions:

  • GET at "/map" - retrieve list of user's pictures from local database; token required on incoming request
  • GET at "/map/update" - retrieve list of user's pictures from Instagram. If new user, add to database. If existing user, compare Instagram image data to local database & add new pictures. Does not delete any old/outdated picture data on local database that user deleted off Instagram
  • POST at "/map" - post a single datapoint to a user; token required on incoming request
  • DELETE at "/map/refresh" - reads user identity off incoming token, wipes local database of all their picture data, then downloads user picture data from Instagram; a way to sync local database with Instagram if user has deleted pictures off Instagram
  • Function for calling Instagram API for user picture data, formatting to shape local database can recognize, is in pictureHelper.js, called "instaImport"

• A third router, authRouter, is for Passport & Instagram to verify users

  • Users first hit the /instagram router endpoint, and pass through the passport.authenticate function
  • They're then automatically routed to the /instagram/callback endpoints, where our database starts adding them

• At the /instagram/callback endpoint, Instagram sends back user data, such as username, instagram id, an access token, user's bio, etc, which we save in the database

  • if a user already exists in the database, helper.findUserById finds them and they're routed to the front end preloader, which sends them to the dashboard
  • if they do not exist, the .catch activates, and helper.postNewUser adds their Instagram data to the database, then runs helper.findUserById to locate them and send front end their token.

Server

Rundown of file structure:

• api
  • server file + Jest test files
• data
  • migration tables, seed files, database config file, and database
• middleware - where the authentication token is decoded
  • Token generated in security file, /security/gen-token.js
  • auth-middlware.js is imported into server.js as tokenCheck, used on the /user and /map endpoints for security
• router_auth
  • authentication folder. Where passport routes user and returning users through instagram's verification URLs/process
  • /instagram -> routed to ./instagram/callbak, where backend starts working
• router_Pictures
  • router + helper functions for the /map endpoint
• router_User
  • router + helper functions for the /user endpoint
• security
  • JS file that generates the token front end uses for user identification