Open for hireContact me
Last updated:
12 min read
Let's build and deploy a full stack MERN web application
Rakesh Potnuru
Author
0%
SHARE

Let's build and deploy a full stack MERN web application

I am sure that when you first begin learning full stack web development using the MERN stack, you will have questions like "What is it like to build a full stack application?" What exactly are frontend and backend? How do we connect them? Is there any magic? etc., So I'm writing this tutorial to address your queries and show you how to build a full-stack web application.

Note: The goal of this tutorial is to provide you with a high-level overview of what it's like to build a full stack application, rather than a detailed explanation of MERN stack technologies.

Let's get started

Prerequisites

  • Basic understanding of MERN stack technologies.
  • NodeJs installed
  • MongoDB account.

The Project

To keep things simple while covering more concepts, we will create a simple mini-project. We will create a simple Productivity Tracker application in which you can record what activities you accomplished during the day and for how much time. So that we may see how we are spending our time. We can also see all of the stuff on the home page.

project demo

How does this work?

  • You enter an activity and the amount of time you spent on it.
  • The data is then submitted to the NodeJs backend.
  • That information will be stored in the MongoDB database.
  • All activities are displayed on the homepage.

application flow

We know what we need to do; now let's figure out how to do it.

Frontend/Client

What is a Frontend/Client application?

Client application refers to the frontend part of a full-stack application. The client sends requests to the server and receives responses. That request could be the client sending information to the server orΒ asking for information. The client is the visible part of a full-stack application.

Let's start by making a client.

  • Make a new folder and label it "productivity-app."

  • Create a react app called "client" using create-react-app.

    npx create-react-app client
  • Start your coding editor/IDE and open the project.

  • This is how your folder structure will look.

    . β”œβ”€β”€ README.md β”œβ”€β”€ package-lock.json β”œβ”€β”€ package.json β”œβ”€β”€ public β”‚ β”œβ”€β”€ favicon.ico β”‚ β”œβ”€β”€ index.html β”‚ β”œβ”€β”€ logo192.png β”‚ β”œβ”€β”€ logo512.png β”‚ β”œβ”€β”€ manifest.json β”‚ └── robots.txt └── src β”œβ”€β”€ App.css β”œβ”€β”€ App.js β”œβ”€β”€ App.test.js β”œβ”€β”€ index.css β”œβ”€β”€ index.js β”œβ”€β”€ logo.svg β”œβ”€β”€ reportWebVitals.js └── setupTests.js
  • For the time being, we are only interested in the App.js and App.css files.

  • Remove all existing code from the App.js and App.css files. Let's make a react component.

  • Add the App component to the App.js file.

    1import "./App.css"; 2 3const App = () => { 4 return <div>My App</div>; 5} 6 7export default App;
  • The above code creates and renders the App component.

  • Run the following command in the terminal and navigate to http://localhost:3000.

    npm start

my app

Design the app.

  • We want the user to enter the name of the activity as well as the time it took. Then we'll display all of the activities on the homepage.

  • Copy and paste this HTML code into the App component.

    1... 2<div className="app"> 3 <header className="app-header"> 4 <h1>Productivity Tracker</h1> 5 <form> 6 <div> 7 <label htmlFor="activity">Activity:</label> 8 <input 9 type="text" 10 id="activity" 11 name="activity" 12 autoComplete="off" 13 /> 14 </div> 15 <div> 16 <label htmlFor="time">Time Taken:</label> 17 <input type="text" id="time" name="time" autoComplete="off" /> 18 </div> 19 <button type="submit">Add</button> 20 </form> 21 </header> 22 <main className="app-main"> 23 <h2>Today</h2> 24 <ol> 25 <li> Activity 1 - 3 hours</li> 26 <li> Activity 2 - 10 min</li> 27 <li> Activity 3 - 2 hours and 25 min</li> 28 </ol> 29 </main> 30</div> 31...
  • Our app will now look like this.

skeleton app

  • Let us now add some CSS. Copy and paste the CSS code from this file into the App.css file.

  • Our app now appears as follows.

app with css

Add logic.

  • The activities are currently hard coded. So let's save and use activities in a state.

    1... 2const [activities, setActivities] = useState([]); 3... 4 5... 6<main className="app-main"> 7<h2>Today</h2> 8 9{activities && activities.length > 0 ? ( 10 <ol> 11 {activities.map((activity) => ( 12 <li key={activity._id}> 13 {activity.name} - {activity.time} 14 </li> 15 ))} 16 </ol> 17) : ( 18 <p>No activities yet</p> 19)} 20</main> 21...

But, Where do we get our activities? How do we add an activity to the list? A backend is required to handle all of this.

Backend/Server

The backend component of a full stack application is frequently referred to as the Server. A server's job is to continuously listen to requests, implement some business logic, and return the results.

Database

Let's create a database first before we create a server. To record and add our activities, we need a database. We can use a cloud database instead of hosting a database. MongoDB offers a free cloud database (atlas) that may be used for small/hobby projects.

  • Log in to your MongoDB account.
  • Create a project.

create project

  • Then go to "Browse collections" and create a database. For the collection name, write "activities".

create a database

  • Click on "Overview" and then in the overview tab click on "CONNECT" -> "Connect your application". Copy the connection string. Your connection string should look like this.

    mongodb+srv://<username>:<password>@<clusterUrl>/<databaseName>?retryWrites=true&w=majority
  • Save this string somewhere safe.

Server

We now have a database. Let us now build our application logic and connect it to the database.

  • Make a folder called "Server" in your project folder.

  • In the terminal, open the folder and type npm init. Fill inΒ all the details.

  • Install the following packages.

    npm i express mongoose dotenv
    • express: Used to create a server.
    • mongoose: Used to work with MongoDB database
    • dotenv: Used to load environment variables.
  • Make a .env file and save your connection string in a variable called "MONGODB URI".

    MONGODB_URI=yourconnectionstring
  • Create a server.js file and paste this code.

    1const express = require("express"); 2const mongoose = require("mongoose"); 3 4const app = express(); 5 6/* Loading the environment variables from the .env file. */ 7require("dotenv").config(); 8 9const PORT = process.env.PORT || 5000; 10const MONGODB_URI = process.env.MONGODB_URI || "mongodb://localhost/todoapiDB"; 11 12 /* Telling the application to use the express.json() middleware. This middleware will parse the body of 13any request that has a Content-Type of application/json. */ 14app.use(express.json()); 15 16/* This is a route handler. It is listening for a GET request to the root route of the application. 17When it receives a request, it will send back a response with the string "Hello World!". */ 18app.get("/", (req, res) => { 19 res.send("Hello World!"); 20}); 21 22/* Connecting to the database and then starting the server. */ 23mongoose 24 .connect(MONGODB_URI, { useNewUrlParser: true }) 25 .then(() => { 26 app.listen(PORT, console.log("Server stated on port 5000")); 27 }) 28 .catch((err) => { 29 console.log(err); 30 }); 31
  • Run the below command and go to http://localhost:5000 in your browser. You will see something like this. (Make sure you have nodemon installed globally.)

    npm run dev

hello world

This means the server is running successfully.

  • Create a schema model to store activity.

    • Create a folder called "models" and in that folder create a file activity.model.js. Copy and paste the below code.

      1const mongoose = require("mongoose"); 2 3const Schema = mongoose.Schema; 4 5/* Creating a new schema for the activity model. */ 6const activitySchema = new Schema({ 7 name: { 8 type: String, 9 required: true, 10 }, 11 time: { 12 type: String, 13 required: true, 14 }, 15}); 16 17module.exports = mongoose.model("Activity", activitySchema);
  • Implement application logic in controllers.

    • Create a folder called "controllers" and in that folder create a file activity.controller.js.

    • We need to implement two things - 1) Get all activities to show on the homepage and 2) Add an activity.

      1const Activity = require("../models/activity.model"); 2 3/** 4 * It's an async function that uses the Activity model to find all activities and then returns a status of 200 with the activities in the response body. 5 */ 6const getActivities = async (req, res) => { 7 try { 8 const activities = await Activity.find(); 9 res.status(200).json(activities); 10 } catch (err) { 11 res.status(500).json({ message: err.message }); 12 } 13}; 14 15/** 16 * It creates a new activity and saves it to the database. 17 */ 18const addActivity = async (req, res) => { 19 const activity = new Activity(req.body); 20 21 try { 22 const newActivity = await activity.save(); 23 res.status(201).json(newActivity); 24 } catch (err) { 25 res.status(400).json({ message: err.message }); 26 } 27}; 28 29module.exports = { 30 getActivities, 31 addActivity, 32}; 33
  • Register routes to handle requests.

    • Create a folder called "routes" and in that folder create a file activity.route.js. Copy and paste the below code.

      1const express = require("express"); 2 3const { 4 getActivities, 5 addActivity, 6} = require("../controllers/activity.controller"); 7 8const router = express.Router(); 9 10/* Creating a route for the get request. */ 11router.get("/activities", getActivities); 12/* Creating a route for the post request. */ 13router.post("/activity", addActivity); 14 15module.exports = router;
  • Final folder structure will be like this.

    . β”œβ”€β”€ controllers β”‚ └── activity.controller.js β”œβ”€β”€ models β”‚ └── activity.model.js β”œβ”€β”€ routes β”‚ └── activity.route.js β”œβ”€β”€ package-lock.json β”œβ”€β”€ package.json └── server.js
  • Use the above routes in the app.

    • Open the server.js file and use the registered routes.

      1... 2const ActivityRouter = require("./routes/activity.route"); 3... 4 5... 6/* Telling the application to use the ActivityRouter for any requests that start with "/api". */ 7app.use("/api", ActivityRouter); 8...
  • Our backend is now wholly operational; we can add and retrieve data. Let's look at how to connect the backend to the front end.

Connecting client and server

It is not difficult to connect the client and server. It's as simple as adding a URL.

  • Navigate to the client folder and create a .env.local file. Paste the backend URL into a variable.

    REACT_APP_BACKEND_URL=http://localhost:5000/api
  • Navigate to the client folder and open App.js. When the user clicks the Add button, we must make a POST request to the server via the /api/activity route.

    • Create a function called handleSubmit() and add the onSubmit attribute to the form element.

    • In this function, we must send a request to the server, passing the activity name and time through the body.

      1... 2const addActivity = async (event) => { 3event.preventDefault(); 4 5const newActivity = { 6 name: event.target.activity.value, 7 time: event.target.time.value, 8}; 9 10await fetch(`${process.env.REACT_APP_BACKEND_URL}/activity`, { 11 method: "POST", 12 headers: { 13 "Content-Type": "application/json", 14 }, 15 body: JSON.stringify(newActivity), 16}); 17 18event.target.activity.value = ""; // sets input empty after clicking submit 19event.target.time.value = ""; // sets input empty after clicking submit 20window.location.reload(); // reloads the window after sending request 21}; 22... 23 24... 25 <form onSubmit={addActivity}> 26...
  • Enter an activity name and time, then submit. (Ensure that the server is also up and running.)

  • An error message will appear in the browser console.

cors error

  • Access to the server is banned by CORS (Cross-Origin Resource Sharing) policy, which means your server does not allow access to its resources. We may avoid this problem by using the cors npm package.

    • Open the server folder and install the cors package.

      npm i cors
    • Then use this package in server.js.

      1... 2const cors = require("cors"); 3... 4 5... 6/* Allowing the frontend to access the backend. */ 7app.use(cors()); 8...
    • Restart the server.

  • Try to add activity. It will work this time.

  • You can see the data that has been added to the database.

data added

  • Now we must display the list of newly added activities.
    • We must display activities as soon as the component renders. We can accomplish this by using useEffect() hook. Fetch the data from the server and save it to the state.

      1... 2 /* Fetching the data from the backend and setting the state of activities to the data. */ 3 useEffect(() => { 4 const fetchData = async () => { 5 const result = await fetch( 6 `${process.env.REACT_APP_BACKEND_URL}/activities` 7 ); 8 const data = await result.json(); 9 setActivities(data); 10 }; 11 fetchData(); 12 }, []); 13...
    • Now you can see all the activities on the homepage.

activities

Hosting full-stack application

Before hosting, we must keep secrets safe and avoid committing unnecessary files/folders.

  • Open the server folder.
  • Initialize git, create a .gitignore file and paste the following stuff.
node_modules .env

Backend

Heroku will be used for the backend.

  • Create a GitHub repository for the server application and push server code to it.
  • Access Heroku.
  • Select "New" -> "Create new app."
  • Give your app a name, choose a region, and then click "Create app."
  • Navigate to Settings -> Config Vars -> Reveal Config Vars -> Add Environment Variables Here.
  • Go to Overview and select GitHub as the deployment mechanism. If you haven't already, sign up for GitHub.
  • Select your repository.
  • Select "Enable Automatic Deploys" if you wish to create a deployment every time you commit to the repository. Finally, click "Deploy Branch."
  • Make a note of the URL of the deployed site.

Frontend

Netlify will host our client/frontend part.

  • Create a GitHub repository for the client application and push client code to it.
  • Sign in to Netlify.
  • Select "Add Site."
  • SelectΒ "GitHub."

Connect to Git provider

  • Give GitHub permission.

  • Select your repository.

  • In "Basic build settings",

    • For base directory - Leave empty.
    • For build command - npm run build
    • For publish directory - "build"
  • Select "Show advanced" -> "New variable" In the key field, enter the REACT_APP_BACKEND_URL and the previously copied backend URL in the value field. Put /api at the end of the URL.

  • Select "Deploy site."

  • That's all! Open the URL in your browser and have fun πŸŽ‰πŸŽ‰.


Add your own features and share the URL in the comments.


Also read:


I hope this has given you an idea of how to develop a full-stack MERN application.

Don't forget to subscribe to my Newsletter.

Thank you!


LEAVE A COMMENT OR START A DISCUSSION

MORE ARTICLES

Introducing Publish Studio: Power Digital Content Creation

    3 min read

Introducing Publish Studio: Power Digital Content Creation

Say β€œHi” to Publish Studio, a platform I’ve building for the past few months. If you are a content writer, then you should definitely check it out. And if you are someone who has an audience on multiple blogging platforms and need an easy way to manage your content across platforms, then you should 100% give it a try.

Let's Build a Full-Stack App with tRPC and Next.js 14

    10 min read

Let's Build a Full-Stack App with tRPC and Next.js 14

Are you a typescript nerd looking to up your full-stack game? Then this guide is for you. The traditional way to share types of your API endpoints is to generate schemas and share them with the front end or other servers. However, this can be a time-consuming and inefficient process. What if I tell you there's a better way to do this? What if I tell you, you can just write the endpoints and your frontend automatically gets the types?

Subscribe to Newsletter

Weekly


  • Never miss an update.
  • Get articles and snippets directly to your inbox.
  • Subscribe to stay connected and avoid getting lost among millions of websites.

Monthly


  • Coming soon...