Is there a reason for this? Looks a bit funny.
https://github.com/esraajb/oh-auth/blob/master/src/routes.js#L10-L14

Please remove
https://github.com/esraajb/oh-auth/blob/master/src/routes/results.route.js#L34
https://github.com/esraajb/oh-auth/blob/master/src/routes/results.route.js#L41
https://github.com/esraajb/oh-auth/blob/master/src/routes/results.route.js#L42

You might want to take that out to a separate file, to leave only server settings in server.js

{{!< layout/default}} should be {{!< layouts/default}}

'Database built' is logged before the database is built. Perhaps change the message to 'Database building...' as 'Database is built' before the database has has a chance to be built

https://github.com/esraajb/oh-auth/blob/master/src/db_build.js#L19

As per the second pic here:
https://github.com/FAC9/notes/blob/master/week8-oauth/project-workflow.md#Oauth-workflow-with-project-(Github)-example

Make this project look pretty!

I love the fact that you have separated your server logic and your database logic, but your naming for the byUserId/getUser/userQuery function is confusing.

I think you should just call the function getUser, the file should be called getUser.js and you should require it in to your server.js file as getUser

Also, it's quite a small point, but I think the signature for this function should be different.

If you look at the examples from the pg module, their functions follow an argument convention with the cb as the last argument.

So instead of having getUser as

const byUserId = (cb, userId) => {

I think it should be

const byUserId = (userId, cb) => {

Can we have a quick check to see where we are and prioritise tasks to get our minimum viable product?

header.html and login.route.js

Wouldn't it be better to store these as integer data type, rather than text?

Its good to try and tidy up things that you dont need as you go along otherwise its really easy to forget about them

https://github.com/esraajb/oh-auth/blob/master/src/routes.js#L5-L6

• Read GitHub API documentation to find specific queries

• Find specific information from GitHub API for specific user.

In velocity function on user_page.js

• Create index.html

• Create main.css

• Create index.js

• Create handlebars template

You could use them here:
https://github.com/esraajb/oh-auth/blob/master/src/routes/user_page.js#L37

Here's a link

• This one is about http wrapper
• This one is the handler that processes the user data that comes back from github

Endpoints to create:

• /
• /login
• /results (redirect uri)
• /logout

There is a lot of good logic inside of this size! Perhaps seperate the callbacks (initial post for access token, post for user info, and jwt-sign) into seperate files and require them in

This should not be named 'token', this is just your parsed body
https://github.com/esraajb/oh-auth/blob/master/src/routes/results.route.js#L16

on line 19 token.accessToken is your token

• Don't create the routes, import a module called 'routes.js' for this
• Don't start the server, import a module called 'start.js' for this

• pie chart using google pie charts

• list of closed issues

• list of open issues

• nav bar on top with page title

• log out button/toggle in nav bar

• Create a basic homepage that has a button which will redirect to GitHub for you to log in.

• Add title to page