initial setting

Author: greatSumini

.env

@@ -4,7 +4,7 @@ JWT_SECRET ='p4sta.w1th-b0logn3s3-s@uce'
 
 # Mongo DB
 # Local development
-MONGODB_URI='mongodb://localhost/bulletproof-nodejs'
+MONGODB_URI='localhost:12345'
 
 # Port
 PORT=3000

.gitignore

@@ -10,4 +10,5 @@ npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
 .env
-build
+build
+.ssh

.now/README.txt

@@ -0,0 +1,11 @@
+> Why do I have a folder named ".now" in my project?
+The ".now" folder is created when you link a directory to a ZEIT Now project.
+
+> What does the "project.json" file contain?
+The "project.json" file contains:
+- The ID of the ZEIT Now project that you linked ("projectId")
+- The ID of the user or team your ZEIT Now project is owned by ("orgId")
+
+> Should I commit the ".now" folder?
+No, you should not share the ".now" folder with anyone.
+Upon creation, it will be automatically added to your ".gitignore" file.

.now/project.json

@@ -0,0 +1 @@
+{"orgId":"ZEwQNW2UefGhZgV7QtjeIw3K","projectId":"Qmbr8bbrVmw85Q3L1PVZpdJu28ispomNbTRsC7Bn1DxyXT"}

README.md

@@ -1,95 +1,3 @@
-# Bulletproof Node.js architecture 🛡️
+# react-11th-practice-server
 
-This is the example repository from the blog post ['Bulletproof node.js project architecture'](https://softwareontheroad.com/ideal-nodejs-project-structure?utm_source=github&utm_medium=readme)
-
-Please read the blog post in order to have a good understanding of the server architecture.
-
-Also, I added lots of comments to the code that are not in the blog post, because they explain the implementation and the reason behind the choices of libraries and some personal opinions and some bad jokes.
-
-The API by itself doesn't do anything fancy, it's just a user CRUD with authentication capabilities.
-Maybe we can transform this into something useful, a more advanced example, just open an issue and let's discuss the future of the repo.
-
-## Development
-
-We use `node` version `10.15.0`
-
-```
-nvm install 10.15.0
-```
-
-```
-nvm use 10.15.0
-```
-
-The first time, you will need to run
-
-```
-npm install
-```
-
-Then just start the server with 
-
-```
-npm run start
-```
-It uses nodemon for livereloading :peace-fingers:
-
-# API Validation
- 
- By using celebrate the req.body schema becomes clary defined at route level, so even frontend devs can read what an API endpoint expects without need to writting a documentation that can get outdated quickly.
-
- ```js
- route.post('/signup', 
-  celebrate({
-    body: Joi.object({
-      name: Joi.string().required(),
-      email: Joi.string().required(),
-      password: Joi.string().required(),
-    }),
-  }),
-  controller.signup)
- ```
-
- **Example error**
-
- ```json
- {
-  "errors": {
-    "message": "child \"email\" fails because [\"email\" is required]"
-  }
- } 
- ```
-
-[Read more about celebrate here](https://github.com/arb/celebrate) and [the Joi validation API](https://github.com/hapijs/joi/blob/v15.0.1/API.md)
-
-# Roadmap
-- [x] API Validation layer (Celebrate+Joi)
-- [ ] Unit tests examples
-- [ ] [Cluster mode](https://softwareontheroad.com/nodejs-scalability-issues?utm_source=github&utm_medium=readme)
-- [x] The logging _'layer'_ 
-- [ ] Add agenda dashboard
-- [x] Continuous integration with CircleCI 😍
-- [ ] Deploys script and docs for AWS Elastic Beanstalk and Heroku
-- [ ] Integration test with newman 😉
-- [ ] Instructions on typescript debugging with VSCode
-
-
-# FAQ 
-
- ## Where should I put the FrontEnd code? Is this a good backend for Angular or React or Vue or _whatever_ ?
-
-  [It's not a good idea to have node.js serving static assets a.k.a the frontend](https://softwareontheroad.com/nodejs-scalability-issues?utm_source=github&utm_medium=readme)
-
-  Also, I don't wanna take part in frontend frameworks wars 😅
-
-  Just use the frontend framework you like the most _or hate the least_. It will work 😁
-
- ## Don't you think you can add X layer to do Y? Why do you still use express if the Serverless Framework is better and it's more reliable?
-
-  I know this is not a perfect architecture but it's the most scalable that I know with less code and headache that I know.
-
-  It's meant for small startups or one-developer army projects.
-
-  I know if you start moving layers into another technology, you will end up with your business/domain logic into npm packages, your routing layer will be pure AWS Lambda functions and your data layer a combination of DynamoDB, Redis, maybe redshift, and Agolia.
-
-  Take a deep breath and go slowly, let the business grow and then scale up your product. You will need a team and talented developers anyway.
+리액트 미션 진행시 사용하기 위한 실습용 서버

package-lock.json

@@ -1,7 +1,7 @@
 {
-  "name": "bulletproof-nodejs",
+  "name": "react-11th-practice-server",
   "version": "1.0.0",
-  "description": "Bulletproof node.js",
+  "description": "for ceos 11th react fetch practice",
   "main": "src/app.ts",
   "scripts": {
     "build": "tsc",
@@ -16,23 +16,17 @@
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/santiq/bulletproof-nodejs.git"
+    "url": "git+https://github.com/CEOS-Developers/react-11th-practice-server.git"
   },
   "keywords": [
-    "boilerplay",
-    "cron",
-    "jobs",
-    "js",
-    "javascript",
+    "ceos",
     "typescript",
     "node",
     "express"
   ],
-  "author": "Santiago Quinteros",
+  "author": "Choi Sumin",
   "license": "ISC",
   "dependencies": {
-    "agenda": "^2.0.2",
-    "agendash": "^1.0.0",
     "argon2": "^0.21.0",
     "body-parser": "^1.18.2",
     "celebrate": "^9.1.0",
@@ -57,7 +51,6 @@
     "winston": "^3.2.1"
   },
   "devDependencies": {
-    "@types/agenda": "^2.0.4",
     "@types/express": "^4.16.0",
     "@types/jest": "^23.3.8",
     "@types/lodash": "^4.14.118",
@@ -77,7 +70,7 @@
     "typescript": "^3.1.3"
   },
   "bugs": {
-    "url": "https://github.com/santiq/bulletproof-nodejs/issues"
+    "url": "https://github.com/CEOS-Developers/react-11th-practice-server/issues"
   },
-  "homepage": "https://github.com/santiq/bulletproof-nodejs#readme"
+  "homepage": "https://github.com/CEOS-Developers/react-11th-practice-server#readme"
 }

package.json

@@ -1,14 +1,12 @@
 import { Router } from 'express';
 import auth from './routes/auth';
 import user from './routes/user';
-import agendash from './routes/agendash';
 
 // guaranteed to get dependencies
 export default () => {
-	const app = Router();
-	auth(app);
-	user(app);
-	agendash(app);
+  const app = Router();
+  auth(app);
+  user(app);
 
-	return app
-}
+  return app;
+};

src/api/index.ts

@@ -1,15 +1,16 @@
 import { Container } from 'typedi';
 import mongoose from 'mongoose';
 import { IUser } from '../../interfaces/IUser';
+import { getLogger } from '../../loaders/dependencyInjector';
 
 /**
- * Attach user to req.user
+ * Attach user to req.currentUser
  * @param {*} req Express req Object
  * @param {*} res  Express res Object
  * @param {*} next  Express next Function
  */
 const attachCurrentUser = async (req, res, next) => {
-  const Logger = Container.get('logger');
+  const Logger = getLogger();
   try {
     const UserModel = Container.get('userModel') as mongoose.Model<IUser & mongoose.Document>;
     const userRecord = await UserModel.findById(req.token._id);