server.js

const express = require('express');
const bcrypt = require('bcrypt-nodejs'); // very common
const cors = require('cors');
const knex = require('knex'); 

// Importing the functions that handle the different routes (in the controllers folder)
const register = require('./controllers/register');
const signin = require('./controllers/signin');
const profile = require('./controllers/profile');
const image = require('./controllers/image');

process.env.NODE_TLS_REJECT_UNAUTHORIZED = 0; 
// Note that this is not secure for use in production, and to only use for local development (which isn't a big issue for us because this is a personal project app with no real users)

// knex.js is an NPM package that allows you to connect to your database. 
const db = knex({
  client: 'pg',
  connection: {
    connectionString : process.env.DATABASE_URL, 
    // This is the database on Heroku
    // It was localhost 127.0.0.1 (home) during development
    // How can I access this database now that the app is in production on Heroku?
    ssl: true
    // This was used during development
    // user : 'joebuono', // there's not really a user
    // password : '',
    // database : 'smart-brain'
  }
});

// This line sets up a server? Where/how exactly?
// A server accepts requests and returns responses in a specific way (must have headers, etc)
const app = express();
// Command click through to check the library code

// What exactly is middleware?
// When a request comes to this server, does the code in this file execute synchronously, so that every request goes through the middleware?
app.use(express.json());
app.use(cors());

app.get('/', (req, res) => {
  res.send('It is working!');
})

// Oooh this is sleek
// handleSignin is a function that returns a function that takes req and res params (see signin.js), 
// and then the req and res params are passed into the returned function (automatically?)
// wow, higher order functions!
// these define endpoints to trigger request/response cycles
// this trusts that express.js will run it for you
app.post('/signin', signin.handleSignin(db, bcrypt));

// this is called "dependency injection"
// we're injecting whatever dependencies this handleSignin function needs
app.post('/register', (req, res) => { register.handleRegister(req, res, db, bcrypt)});

// a possible endpoint for a profile page for each user
app.get('/profile/:id', (req, res) => { profile.handleProfile(req, res, db)});

app.put('/image', (req, res) => { image.handleImage(req, res, db)});

app.post('/imageurl', (req, res) => { image.handleApiCall(req, res)});


app.listen(process.env.PORT || 3000, () => {
  console.log(`app is running on port ${process.env.PORT}`);
})



/*
Creating different endpoints:
/ --> res = this is working (root route)
/signin --> POST = success/fail
/register --> POST = user
/profile/:userId --> GET = user
/image --> PUT --> user (count)



Build your server, test with Postman, and then, only at the end once everything is working, connect with the frontend. 

Ohhh wait a second...
- Postman is like a pretend front end. 



*/

/*

  // for encrytion:
  // bcrypt.compare(password, hash, function(err, res) {
  //   //
  // });
  // bcrypt.compare(password, hash, function(err, res) {
  //   //
  // });



  bcrypt.hash(password, null, null, function(err, hash) {
    console.log(hash);
  });

*/