Changes on server.js

[jzunigarce]

@gbowne1 I have made some changes in the server.js file, taking advantage of the fact that we had an app.js file, I placed the entire app in it, while in the server.js I only placed the server startup. I also added a new variable in the .env file to specify the port through which the server will run (in case of not setting this variable it will default to 3000).
However, I see that with the changes that the other devs have uploaded, possibly some conflicts are added because some files were modified.

[gbowne1]

Eventually we can use app.js and index.js on both sides to control the majority of the app. The server would have both app.js and index.js and the client would have app.js and index.js. which is kinda like how React does it. And we could still keep and use the server.js Each app.js would house each sides app. The index.js would be sent to the browser and serves as a router to the browser. Each page would provide a index.js in the same way that index.html would provide routing on the browser and fill in its web components.

At least that's how it was described to me.

I figured there might be some conflicts from tonight's merges. We can work around that as we clean up the app. Still a lot of functionality to add.

@jzunigarce @Joywin2412

[gbowne1]

The login process needs a bunch of refactoring from the point where the app loads the initial screen at the root of localhost up till the point where you would eventually get the dashboard.

A lot of stuff actually works now, where before it never worked.

The dashboard needs some work

We need to add the reusable web components the navbar and the left sidebar/sidenav and clean up the topnav navbar which would include adding the hamburger bars icon which would open the drawer.

@jzunigarce @Joywin2412