{ "componentChunkName": "component---src-templates-blog-post-js", "path": "/implement-jwt-based-user-authentication-in-a-mern-stack-app-part-7/", "result": {"data":{"markdownRemark":{"html":"
\n\n
\n
This blog post is part of a series. You must finish part-1, part-2, part-3, part-4, part-5 & part-6 before continuing here.
\n

We will use mongoose to interact with our database. Mongoose will act as the frontend to our MongoDB database.

\n
\n

What is mongoose?
\nMongoose is what is known as an Object Data Model (ODM). An ODM represents the website’s data as JavaScript objects, which are then mapped to the underlying database.
\nODMs are often slower because they often use translation code to map between objects and the database format. The benefit of using an ODM is that programmers can continue to think in terms of JavaScript objects rather than database semantics. Moreover, using an ODM often results in lower costs for development and maintenance.

\n
\n

Sign in to your MongoDB Atlas account. In the clusters view, click on CONNECT.

\n

\n \n \n \n \n

\n

Then, click on Connect your application.

\n

\n \n \n \n \n

\n

Back to our application, create a .env file in the mern-auth folder.\nIn the .env file, paste the connection string that you copied from MongoDB Atlas as the value of the key MONGO_URI. Don’t place the connection string within double quotes.

\n
mern-auth/.env
\n
MONGO_URI=mongodb+srv://sundaray:<password>@sandbox.y8blv.mongodb.net/myFirstDatabase?retryWrites=true&w=majority
\n

Replace <password> with the password that you have set for the database user. And replace myFirstDatabase with the name of your database.

\n

What is a .env file?

\n

.env is a simple configuration text file that is used to define environment variables that we want to pass into our application’s environment. By convention .env variable names are uppercase words separated by underscores. Variable names are directly followed by an =, which in turn is directly followed by the value, for example: VARIABLE_NAME=value.

\n

The .env file will contain secret environment variables that we don’t want to expose to the outside world. If you are using git to push your code to a remote repository such as GitHub you wouldn’t want to push the .env file to GitHub and make it public. Therefore, add the .env file in the .gitignore file.

\n
mern-auth/.gitignore
\n
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.\n\n# dependencies\n**/node_modules\n/.pnp\n.pnp.js\n\n# testing\n/coverage\n\n# production\n/build\n\n# misc\n.env\n.DS_Store\n.env.local\n.env.development.local\n.env.test.local\n.env.production.local\n\nnpm-debug.log*\nyarn-debug.log*\nyarn-error.log*
\n

We have stored the connection string in the .env file. Next, we will use mongoose to connect to our MongoDB database.

\n

Connecting to MongoDB

\n

First, we need to install mongoose.

\n
PS C:\\Users\\Delhivery\\Desktop\\mern-auth> npm i mongoose
\n

Note that installing mongoose adds all its dependencies including the MongoDB database driver. The MongoDB Node.js driver allows Node.js applications to connect to MongoDB and work with data.

\n

We also need to install a module called dotenv that will help us load the environment variables we have defined inside the .env file into process.env.

\n
 PS C:\\Users\\Delhivery\\Desktop\\mern-auth> npm i dotenv
\n
\n

Note that you can install multiple npm packages with a single command. All we need to do is to use the npm install command followed by multiple package names separated by spaces, as shown below:

\n
\n
PS C:\\Users\\Delhivery\\Desktop\\mern-auth> npm i mongoose dotenv
\n

Inside the server folder, create a folder named config and inside the config folder create a file named db.js and paste the following code snippet in that file.

\n
server/config/db.js
\n
const mongoose = require("mongoose")\nconst dotenv = require("dotenv")\n\ndotenv.config()\n\nconst connectDB = async () => {\n  try {\n    const conn = await mongoose.connect(process.env.MONGO_URI, {\n      useNewUrlParser: true,\n      useCreateIndex: true,\n      useUnifiedTopology: true,\n    })\n    console.log(`MongoDB connected: ${conn.connection.host}`)\n  } catch (error) {\n    console.error(`Error: ${error.message}`)\n    process.exit(1)\n  }\n}\n\nmodule.exports = connectDB
\n

Mongoose requires a connection to our MongoDB database. We connect to our MongoDB database using mongoose.connect method. The first argument to the connect method is our connection string.

\n

The dotenv module loads the environment variables that we have defined inside the .env file as key-value pairs inside process.env. Therefore, we can access our connection string using process.env.MONGO_URI.

\n

We can programmatically terminate a Node.js application by using the exit method of the process core module. When Node.js runs this line, the process is immediately forced to terminate. We can also pass an integer that signals the operating system the exit code.

\n

Go to part-8

\n","frontmatter":{"title":"Implement JWT Based User Authentication in a MERN Stack App - Part 7","date":"2021-05-23"}}},"pageContext":{"slug":"/implement-jwt-based-user-authentication-in-a-mern-stack-app-part-7/","prev":{"fields":{"slug":"/implement-jwt-based-user-authentication-in-a-mern-stack-app-part-6/"},"frontmatter":{"modules":null}},"next":{"fields":{"slug":"/implement-jwt-based-user-authentication-in-a-mern-stack-app-part-8/"},"frontmatter":{"modules":null}}}}, "staticQueryHashes": ["3159585216"]}