From c05914b49ed598e1328e4ca1caa79c23485f3016 Mon Sep 17 00:00:00 2001
From: Ken Desrosiers <36285260+KenDesrosiers@users.noreply.github.com>
Date: Sun, 15 Sep 2019 11:47:40 -0400
Subject: [PATCH 1/6] Update README.md

---
 README.md | 41 -----------------------------------------
 1 file changed, 41 deletions(-)

diff --git a/README.md b/README.md
index afcca619..dbfd4e2e 100755
--- a/README.md
+++ b/README.md
@@ -1,44 +1,3 @@
-Assignment 3 - Persistence: Two-tier Web Application with Flat File Database, Express server, and CSS template
-===
-
-Due: September 16th, by 11:59 AM.
-
-This assignnment continues where we left off, extending it to use the most popular Node.js server framework (express), a flat file database suitable for small applications (lowdb), and a CSS application framework / template of your choice (Boostrap, Material Design, Semantic UI, Pure etc.)
-
-
-Baseline Requirements
----
-
-Your application is required to implement the following functionalities:
-
-- a `Server`, created using Express (no alternatives will be accepted for this assignment)
-- a `Results` functionality which shows the entire dataset residing in the server's memory
-- a `Form/Entry` functionality which allows users to add, modify, and delete data items (must be all three!) associated with their user name / account.
-- Use of at least five [Express middleware packages](https://expressjs.com/en/resources/middleware.html). Explore! 
-- Basic authentication using the [Passport middleware](http://www.passportjs.org) for Express (this counts as one of your five middleware packages). We encourage using the Local strategy, but OAuth (Open Authentication) can also be used for additional technical achievement. The course staff cannot help you with the various flavors of OAuth strategies. YOU MUST PROVIDE US WITH ACCOUNT CREDENTIALS TO LOGIN TO YOUR APPLICATION IF YOU USE OAUTH. The course staff cannot be expected to have credentials for any particular OAuth service.
-- Persistent data storage in between server sessions. [lowdb](https://github.com/typicode/lowdb) is a suitable database package for this assignment and will be discussed in class.
-- Use of a [CSS framework or template](https://github.com/troxler/awesome-css-frameworks). This should do the bulk of your styling/CSS for you and be appropriate to your application. For example, don't use [NES.css](https://nostalgic-css.github.io/NES.css/) (which is awesome!) unless you're creating a game or some type of retro 80s site.
-
-Your application is required to demonstrate the use of the following concepts:
-
-HTML:
-- HTML input tags and form fields of various flavors (`<textarea>`, `<input>`, checkboxes, radio buttons etc.)
-- HTML that can display all data *for a particular authenticated user*. Note that this is different from the last assignnment, which required the display of all data in memory on the server.
-
-Note that it might make sense to have two simple pages for this assignment, one that handles login / authentication, and one that contains the rest of your application. For this assignment, it is acceptable to simply create new user accounts upon login if none exist, however, you must alert your users to this fact. If you're not using OAuth 
-
-CSS:
-- CSS styling should primarily be provided by your chosen template/framework. Oftentimes a great deal of care has been put into designing CSS templates; don't override their stylesheets unless you are extremely confident in your graphic design capabilities. The idea is to use CSS templates that give you a professional looking design aesthetic without requiring you to be a graphic designer yourself.
-
-JavaScript:
-- At minimum, a small amount of front-end JavaScript to get / fetch data from the server. See the [previous assignment](https://github.com/cs4241-19a/a2-shortstack) for reference.
-
-Node.js:
-- A server using Express, at least five pieces of Express middleware, and a persistent database (a flat file using lowdb is great).
-
-Deliverables
----
-
 Do the following to complete this assignment:
 
 1. Implement your project with the above requirements. A good potential starting point is to use the "hello-express" project template inside of Glitch; this appears as an option when you hit the "New Project" button. Use the work you did in the last assignment as a reference to implement functionality, as well as the notes from class on 9/9 and 9/12.

From 170bfd09ab859f2b84950fe11b2aa26bf66ac265 Mon Sep 17 00:00:00 2001
From: Ken Desrosiers <36285260+KenDesrosiers@users.noreply.github.com>
Date: Sun, 15 Sep 2019 12:03:30 -0400
Subject: [PATCH 2/6] Update README.md

---
 README.md | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/README.md b/README.md
index dbfd4e2e..2472bfa0 100755
--- a/README.md
+++ b/README.md
@@ -1,11 +1,4 @@
-Do the following to complete this assignment:
-
-1. Implement your project with the above requirements. A good potential starting point is to use the "hello-express" project template inside of Glitch; this appears as an option when you hit the "New Project" button. Use the work you did in the last assignment as a reference to implement functionality, as well as the notes from class on 9/9 and 9/12.
-2. If you developed your project locally, deploy your project to Glitch, and fill in the appropriate fields in your package.json file.
-3. Test your project to make sure that when someone goes to your main page on Glitch, it displays correctly.
-4. Ensure that your project has the proper naming scheme `a3-yourname` so we can find it.
-5. Fork this repository and modify the README to the specifications below. You do not need to include any of your project files in this repo (we will see those on Glitch), you only need to update and commit the README file.
-6. Create and submit a Pull Request to the original repo. Name the pull request using the following template: `a3-gitname-firstname-lastname`.
+`a3-gitname-firstname-lastname`.
 
 Sample Readme (delete the above when you're ready to submit, and modify the below so with your links and descriptions)
 ---

From 4825dda66fecd350dfce8100eb32979e8a8bb647 Mon Sep 17 00:00:00 2001
From: Ken Desrosiers <36285260+KenDesrosiers@users.noreply.github.com>
Date: Sun, 15 Sep 2019 12:22:02 -0400
Subject: [PATCH 3/6] Update README.md

---
 README.md | 21 ++++++---------------
 1 file changed, 6 insertions(+), 15 deletions(-)

diff --git a/README.md b/README.md
index 2472bfa0..5e3ef2b6 100755
--- a/README.md
+++ b/README.md
@@ -3,24 +3,15 @@
 Sample Readme (delete the above when you're ready to submit, and modify the below so with your links and descriptions)
 ---
 
-## Your Web Application Title
+## Ken's Ice Cream Shop (Ver. 2)
 
-your glitch link e.g. http://a3-charlieroberts.glitch.me
+http://a3-kendesrosiers.glitch.me
 
-Include a very brief summary of your project here. Images are encouraged, along with concise, high-level text. Be sure to include:
-
-- the goal of the application
-- challenges you faced in realizing the application
-- what authentication strategy / database you chose to use and why (choosing one because it seemed the easiest to implement is perfectly acceptable)
-- what CSS framework you used and why.
-  - include any modifications to the CSS framework you made via custom CSS you authored.
-- the five Express middleware packages you used and a short (one sentence) summary of what each one does.
+For this project, I built on what I did for project 2 and made my game a whol lot better and more user friendly. Most notibly, I got rid of the wonky drag/drop functionality and replaced it with registering different key presses associated with different flavors. This makes the game a lot easier to play. I faced a lot of challanges with getting the local authentication to work. For my app, I feel like the logging in functionality is kind of pointless, and I wouldn't have made a game if I knew we were going to implement a user authentication system. I did however really like the idea of persistent data storage. I went with the recommended lowdb, and I used it in order to have a persistant scoreboard. I used authentication to allow an admin to modify and delete entries from the scoreboard. Also, I ended up going with JWT (JSON Web Token) based authentication. For the quick login to change the scoreboard, I feel like the local strategy/storing cookies and creating sessions was a bit too complicated, so a token-based authentication worked just fine. I also had a bit of a hard time understanding the session/cookie idea. I used nes.css as my CSS framework because I already had the 8-bit styling last time. This framework helped me convert more things to 8-bit styling, like buttons and modals. For Express middleware, I used passport, passport-jwt, body-parser, serve-static, and serve-favicon. passport and passport-jwt were for authenticating the token that I generated with a different module (jsonwebtoken). body-parser was for easy json request/response parsing. serve-static was to help serve whole directories, and serve-favicon was to include a favicon on the tab of the game.
 
 ## Technical Achievements
-- **Tech Achievement 1**: I used OAuth authentication via the GitHub strategy
-- **Tech Achievement 2**: I used over ten Express middleware packages, enabling me to create a server that...
+- **jsonwebtoken**: I used this module in order to take a payload and create a jwt out of it for authentication.
+- **Tech Achievement 2**: I changed the entire functionality of my game from drag/drop to key presses using javascript events.
 
 ### Design/Evaluation Achievements
-- **Design Achievement 1**: I tested my application using screen reading software, and found that...
-- **Design Achievement 2**: I followed best practices for accessibility, including providing alt attributes for images and using semantic HTML. There are no `<div>` or `<span>` elements in my document.
-- **Design Achievement 3**: We tested the application with n=X users, finding that...
+- **level of difficulty**: I used nes.css radio buttons and a modal in order to allow the user to select what level of difficulty they want to play the game at.

From 4844f3db4603e91e43724a77018eb7086bd2266e Mon Sep 17 00:00:00 2001
From: Ken Desrosiers <36285260+KenDesrosiers@users.noreply.github.com>
Date: Sun, 15 Sep 2019 12:23:19 -0400
Subject: [PATCH 4/6] Update README.md

---
 README.md | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/README.md b/README.md
index 5e3ef2b6..97136b16 100755
--- a/README.md
+++ b/README.md
@@ -1,8 +1,3 @@
-`a3-gitname-firstname-lastname`.
-
-Sample Readme (delete the above when you're ready to submit, and modify the below so with your links and descriptions)
----
-
 ## Ken's Ice Cream Shop (Ver. 2)
 
 http://a3-kendesrosiers.glitch.me

From e36ef9bbf8893ba0c988b7d69f267093096484c1 Mon Sep 17 00:00:00 2001
From: Ken Desrosiers <36285260+KenDesrosiers@users.noreply.github.com>
Date: Sun, 15 Sep 2019 12:24:53 -0400
Subject: [PATCH 5/6] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 97136b16..28eebfdc 100755
--- a/README.md
+++ b/README.md
@@ -6,7 +6,7 @@ For this project, I built on what I did for project 2 and made my game a whol lo
 
 ## Technical Achievements
 - **jsonwebtoken**: I used this module in order to take a payload and create a jwt out of it for authentication.
-- **Tech Achievement 2**: I changed the entire functionality of my game from drag/drop to key presses using javascript events.
+- **Javascript events**: I changed the entire functionality of my game from drag/drop to key presses using javascript events.
 
 ### Design/Evaluation Achievements
 - **level of difficulty**: I used nes.css radio buttons and a modal in order to allow the user to select what level of difficulty they want to play the game at.

From 915f3a58af50d4c9fc87e2d51f5ef9d2393c2195 Mon Sep 17 00:00:00 2001
From: Ken Desrosiers <36285260+KenDesrosiers@users.noreply.github.com>
Date: Sun, 15 Sep 2019 14:23:59 -0400
Subject: [PATCH 6/6] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 28eebfdc..5c7bcb39 100755
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 
 http://a3-kendesrosiers.glitch.me
 
-For this project, I built on what I did for project 2 and made my game a whol lot better and more user friendly. Most notibly, I got rid of the wonky drag/drop functionality and replaced it with registering different key presses associated with different flavors. This makes the game a lot easier to play. I faced a lot of challanges with getting the local authentication to work. For my app, I feel like the logging in functionality is kind of pointless, and I wouldn't have made a game if I knew we were going to implement a user authentication system. I did however really like the idea of persistent data storage. I went with the recommended lowdb, and I used it in order to have a persistant scoreboard. I used authentication to allow an admin to modify and delete entries from the scoreboard. Also, I ended up going with JWT (JSON Web Token) based authentication. For the quick login to change the scoreboard, I feel like the local strategy/storing cookies and creating sessions was a bit too complicated, so a token-based authentication worked just fine. I also had a bit of a hard time understanding the session/cookie idea. I used nes.css as my CSS framework because I already had the 8-bit styling last time. This framework helped me convert more things to 8-bit styling, like buttons and modals. For Express middleware, I used passport, passport-jwt, body-parser, serve-static, and serve-favicon. passport and passport-jwt were for authenticating the token that I generated with a different module (jsonwebtoken). body-parser was for easy json request/response parsing. serve-static was to help serve whole directories, and serve-favicon was to include a favicon on the tab of the game.
+For this project, I built on what I did for project 2 and made my game a whole lot better and more user friendly. Most notibly, I got rid of the wonky drag/drop functionality and replaced it with registering different key presses associated with different flavors. This makes the game a lot easier to play. I faced a lot of challanges with getting the local authentication to work. For my app, I feel like the logging in functionality is kind of pointless, and I wouldn't have made a game if I knew we were going to implement a user authentication system. I did however really like the idea of persistent data storage. I went with the recommended lowdb, and I used it in order to have a persistant scoreboard. I used authentication to allow an admin to modify and delete entries from the scoreboard. Also, I ended up going with JWT (JSON Web Token) based authentication. For the quick login to change the scoreboard, I feel like the local strategy/storing cookies and creating sessions was a bit too complicated, so a token-based authentication worked just fine. I also had a bit of a hard time understanding the session/cookie idea. I used nes.css as my CSS framework because I already had the 8-bit styling last time. This framework helped me convert more things to 8-bit styling, like buttons and modals. For Express middleware, I used passport, passport-jwt, body-parser, serve-static, and serve-favicon. passport and passport-jwt were for authenticating the token that I generated with a different module (jsonwebtoken). body-parser was for easy json request/response parsing. serve-static was to help serve whole directories, and serve-favicon was to include a favicon on the tab of the game.
 
 ## Technical Achievements
 - **jsonwebtoken**: I used this module in order to take a payload and create a jwt out of it for authentication.