Chris Klanac cklanac

Passport Local Strategy Auth

In the first lesson, you'll learn all about user management and access control.

We'll use bcryptjs to encrypt user passwords so we don't have to save them as raw text strings.

Note that there are two separate libraries available on NPM `bcryptjs` (the one we want) and `bcrypt` (not what we want). Be sure to install `bcryptjs`, otherwise you may encounter problems on TravisCI.

We'll use Passport to control access to an endpoint at /users/me that only authenticated users can access.

Setup Travis and Heroku CICD: Point-n-Click

Continuous Integration with Travis CI

Configure travis.yml

Run npm test to ensure tests are working correctly locally
Create .travis.yml file in repo
Add the following to configure for node

API Capstone Guidelines:

Build a RESTful API based on the starter repo. Your API should demonstrate the following features:

Resource List: API returns a list of resources.
Resource Details: API returns details of a specific resource
Resource Update: API allows authenticated users to update a resource. You can choose to update the entire resource or just partial subdata like comments, likes or favorites.

npm-run-setups

The primary question is whether npm start and npm test should be setup for developer convenience and other commands like npm run heroku and npm run travis should be setup for services. Or should npm start and npm test should be kept for production and test environments respectively and customer scripts like npm run dev:start and npm run dev:test should be created for development.

The secondary question is... what should they be named?

Below are examples of the scripts at the various phases of the course

	'use strict';

	const express = require('express');
	const router = express.Router();

	const { Cat } = require('./model');

	router.get('/', (req, res) => {
	Cat.find()
	.then(list => {

	# Execute the following using VS Code CodeRunner extentions
	# Or simply Copy and paste the relevent sections into bash

	# set COHORT environment variable
	COHORT=cohort-meta/cohort-2017-06-12.yaml
	echo "" > output.md

	# node generator/generator.js master-syllabus/00-pre-course-reading.md $COHORT 2 1 >> output.md

	: <<'END'

	#!/usr/bin/env bash

	# ~/.macos — https://mths.be/macos

	# Close any open System Preferences panes, to prevent them from overriding
	# settings we’re about to change
	osascript -e 'tell application "System Preferences" to quit'

	# Ask for the administrator password upfront
	sudo -v

	DROP TABLE IF EXISTS items_tags;
	DROP TABLE IF EXISTS tags;
	DROP TABLE IF EXISTS items;
	DROP TABLE IF EXISTS users;


	CREATE TABLE users (
	id serial PRIMARY KEY,
	email text NOT NULL,
	username text NOT NULL

	'use strict';

	const mongoose = require('mongoose');
	mongoose.Promise = global.Promise;

	const { DATABASE_URL } = require('./config');

	mongoose.connect(DATABASE_URL, { useMongoClient: true });

	const favoriteSchema = mongoose.Schema({