jgoldverg/leaseit

leaseit's Issues

Create express api endpoints that will handle the users request to login

So idk about the name of the actual endpoint but google and see if there are naming patterns could be something like /login. Then what this would do is ping the login service which would respond with some type of Http code.

Login Service

This service is an Authentication service. It will have its own private database that will hold all of the current users made. The idea is that it takes an input of credentials such as username and password and it returns a response code and that response needs to be handled. I would look up standards as to what the response type.

Create Postgres table for Users

API-Gateway

This is what the user will ping and then be navigated to whatever kind of data the user is requesting.
Problem: We need a way to have a way for our user to request information from us.

Solution: API's, this API gateway is like the other ones except it has to take care of authentication and the user never goes farther than this. The user requests something and we provide it out by using the proper services. This is a security principle: there is only one way in or out.

Logging Service For our containers

Problem: with many containers how do we check the logs of one if the container crashes and all of written log data is lost. Or another problem is what if some part of our backend dies how do we check what crashed? If the container falls everything is lost.

Solution: Make a service that will be used to log all data and it will have some type of persistent data store. MongoDB lets say bc its great with files. So if we ever need to debug our services we can just look in these logs and not have to ssh into every container hoping its still up.

Add Passport authentication to the application. Not sure if this will conflict with our login service but should integrate the two

Create the respective queries to handle Users and store(username, password) in that volume specified in the docker-compose