Building a backend #20

[asiyani]

This PR adds Nodejs and MongoDB as the backend to this project. Current functionality for this app is not disturbed. After running yarn start website works as it is working now.

• New Folder structure
  • Moved js, css and index.html file to the public folder.
  • Added 3 new folders. server, config and test.
  • server folder contains app.js, db and routes folder.
  • db folder contains schema/model for MongoDB database.
  • routes folder contains js files related to APIs and other web routes
  • config folder got the configuration for dotenv to load Nodejs environment variables.
  • Test folder got test files for nodejs & db. e.g. db.test.js

• MongoDB model

  • for now, there are 3 separate schemas
  • user -> user who is registered/logged in to curiosity website. (git authentication)
  • username -> Schema to store data related to usernames
  • Repository -> schema to store data related to repos.
  • Ideally, we should combine username and repository schema for denormalization? but it depends on the type of query we will be doing. We should discuss that further.

• Routes

  • Just for testing and to get an idea about folder structure, I have created following routes.
  • GET /api/username/all -> will send username list as jason
  • GET /user, GET /user/login, GET /user/logout -> will just print message on web.

• Configuration

  • I have 2 separate files for dotenv settings. .dev.env and .test.env
  • MONGODB_URI is different in both files because we don't want to run lots of test on main db.

• Test

  • I am using Mocha and expect for backend testing.
  • Just a simple test added to make sure we are able to store data to MongoDB server. yarn run test-node

• Readme

  • I have updated README.md file for Getting Started Guide.

Please review this folder structure and code. let me know what you guys think? is DB schema properties enough or we need some additional information? I think we should create another issue to discuss schema design.

[mubaris]

@asiyani Cool work man :+1:

@alejandronanez Should I wait for this PR to merge, so that I can work on Webpack

[alejandronanez]

@alejandronanez Should I wait for this PR to merge, so that I can work on Webpack

Yes sir!

[alejandronanez]

@asiyani fix conflicts on index.html and we should be good to go 👍

[asiyani]

I didnt change anything in index.html just moved it to public folder...

On Fri, 2 Jun 2017, 1:36 pm Alejandro Ñáñez Ortiz, notifications@github.com wrote:

@asiyani https://github.com/asiyani fix conflicts on index.html and we should be good to go 👍

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/curiositylab/curiosity/pull/40#issuecomment-305773624, or mute the thread https://github.com/notifications/unsubscribe-auth/AGz7sOoxkh_CsvCDjmvFtTvIyoCfoRnJks5sAAHLgaJpZM4NtnkN .

[alejandronanez]

I didnt change anything in index.html just moved it to public folder...

Oh well, maybe that's the issue. Anyway we can't merge until that's resolved though :( Let me know if you have any issues with those conflicts maybe I can jump in.

[asiyani]

I need index.html in public folder, otherwise i need to create route for index.html Ideally that file should be in public folder. Do you want me too move it to root for now just to merge PR.and then we move it back to public folder?

[alejandronanez]

What merge conflict are you seeing? Feel free to change whatever you think is necessary to solve the conflict so we can merge your pr. On Fri, Jun 2, 2017 at 7:52 AM Ashok notifications@github.com wrote:

I need index.html in public folder, otherwise i need to create route for index.html Ideally that file should be in public folder. Do you want me too move it to root for now just to merge PR.and then we move it back to public folder?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/curiositylab/curiosity/pull/40#issuecomment-305776947, or mute the thread https://github.com/notifications/unsubscribe-auth/AAcYUk0ekBF1VnDGk1ugDbico3AUbgAdks5sAAV5gaJpZM4NtnkN .

[mubaris]

@asiyani You moved the index.html to public folder. After I made a change in the original index.html. Therefore, the git mv didn't work properly. If you move the new index.html to public folder, it might work.

Thoughts @alejandronanez

[alejandronanez]

Yeah that makes sense! On Fri, Jun 2, 2017 at 9:04 AM Mubaris NK notifications@github.com wrote:

@asiyani https://github.com/asiyani You moved the index.html to public folder. After I made a change in the original index.html. Therefore, the git mv didn't work properly. If you move the new index.html to public folder, it might work.

Thoughts @alejandronanez https://github.com/alejandronanez

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/curiositylab/curiosity/pull/40#issuecomment-305797426, or mute the thread https://github.com/notifications/unsubscribe-auth/AAcYUpRTSHbqwry-C4Pr8Tes_RxxFr8Iks5sABZfgaJpZM4NtnkN .

[asiyani]

conflicts are now resolved.

[alejandronanez]

Good stuff boys