FooDelicious - Recipes Web App

This Recipe Web App is a full-stack application built using the MERN (MongoDB, Express, React, Node.js) stack, developed as part of QueenB’s summer project. It enables users to explore, upload, and manage their own recipes in a personalized and secure environment.

Key features of the app include secure user authentication (sign up and login), a user-specific recipe library, a content upload page, search and filtering options, and profile management, allowing users to edit or delete their profile and view only their own recipes. An intuitive home recipe display simplifies navigation and recipe browsing for a seamless user experience.

The app was developed by a team working collaboratively on Trello and using Git for version control. The project provided valuable hands-on experience in full-stack development and agile teamwork.

Table of Contents

• Installation
  • Prerequisites
  • Clone the Repository
  • Server Setup
  • Client Setup
• Configuration
  • Testing the Template w Random Duck Feature
  • Setting Up MongoDB Atlas
  • Setting Up Environment Variables
• Usage
• Best Practices for Implementing a Full Stack Feature
• Project Structure
• Summary

Installation

Prerequisites

Ensure you have the following installed on your local machine:

• Node.js (version 20.x or higher)
• npm (version 10.x or higher)
• MongoDB - Atlas (see the Setting Up MongoDB Atlas section for details)

Clone the Repository

To get started with this project, you need to clone the repository to your local machine. Follow these steps:

1. Open a Terminal
   • Open your preferred terminal application.
2. Navigate to the Desired Directory:
   • Use the cd command to navigate to the directory where you want to clone the repository. For example:

cd path/to/your/directory

3. Fork this repository - only ONCE per project
4. Clone the forked Repository:
   • Copy your repository URL
   • Run the following command to clone the repository:

git clone <paste-your-repository-url>

4. Navigate to the Project Directory:
   • After cloning, navigate into the project directory:

cd queenb-summer-project-template-24

Server Setup

1. Navigate to the server directory:

cd server

2. Install server dependencies:

npm install

Client Setup

1. Navigate to the client directory:

cd ../client

2. Install client dependencies:

npm install

Configuration

Testing the Template w Random Duck Feature

First, ensure All Dependencies Are Installed for client and server (see installation section).

This template includes a simple feature to display a random rubber duck from example READ ONLY database. This feature demonstrates the integration of the frontend with the backend and can be used to test if your setup is working correctly.

How It Works

1. Client:
   • The home page contains a button labeled "Show Random Duck".
   • When clicked, this button sends a request to the backend to fetch a random rubber duck.
   • The details of the random rubber duck, including its name and image, are displayed on the page.
2. Backend:
   • The server has an endpoint /api/rubberDucks/random that selects a random rubber duck from the database and returns its details in the response.

Configure the Backend

1. Configure Environment Variables for the Backend:
   • Open a terminal and navigate to the server directory:

cd ../server

• Create a .env file in the server.
• Copy the content of .env.example file under the server folder to the .env file.

2. Run the Backend Server in development mode:

npm run dev

Configure the Frontend

1. Configure Environment Variables for the Frontend:
   • Open a terminal and navigate to the client directory:

cd ../client

• Create a .env file in the client.
• Copy the content of .env.example file under the client folder to the .env file.

2. Run the Frontend Client:

npm start

Test the Application:

• Open http://localhost:<client-port-number> (usually at http://localhost:3000) and interact with the application to ensure it works as expected.
• Click the "Show Random Duck" button to retrieve a random duck from the database and display its details on the screen.
• This feature helps verify that your frontend can communicate with the backend and retrieve data from the MongoDB database correctly. If you see the random duck's details displayed on the page, your setup is working properly.
• IMPORTANT NOTE - the example MongoDB connection string attached to the server file grants you a READ ONLY permissions to the rubber duck example database - you only be able to use GET requests, and cannot modify data.

Troubleshooting:

1. Check browser console and network logs for errors.
2. Ensure backend and frontend configurations are correct.

• Feedback:
  • Report any issues or provide feedback for further improvements.

After testing the template and verifying the server and client are working as expected - set yout own project MongoDB configurstion and Evironment variavles:

Setting Up MongoDB Atlas

only once per project.

Creating a New Database in MongoDB Atlas

see video toturial by Net Ninja - Link

1. Sign Up / Log In to MongoDB Atlas:

   • Go to MongoDB Atlas and sign up for a new account or log in if you already have one.

2. Create a New Project:

   • Once logged in, click on "Projects" in the left-hand menu.
   • Click on the "New Project" button.
   • Enter a project name, e.g., "LibraryProject", and click "Next".
   • Add your teamates as project members.
   • Click "create project".

3. Create a New Cluster:

   • Within your new project, click on "Create a Cluster".
   • Choose a cloud provider and region - choose the free plan and the AWS cloud provider.
   • Click "Create Deployment". This process might take a few minutes.

4. Set Up Database Access:

   • Once your cluster is created, you need to set up a user to access the database.
   • Click on the "Database Access" tab.
   • Click the "Add New Database User" button.
   • Create a user with a username and password. Make sure to note these down as you will need them later.
   • Set the user's permissions to "Read and write to any database".

5. Network Access:

   • Click on the "Network Access" tab.
   • Click the "Add IP Address" button.
   • Add your current IP address or allow access from anywhere (0.0.0.0/0) if you're just testing. Be cautious with security when using the latter option.

6. Create a Database:

   • Click on the "Database" tab.
   • Click the "Browse Collections" button next to your cluster.
   • Click "Create Database".
   • Enter a database name, e.g., "libraryDB", and a collection name, e.g., "ducks".
   • Click "Create".

7. Connect to Your Cluster:

   • Go back to the "Database" tab.
   • Click the "Connect" button next to your cluster.
   • Choose "Connect your application".
   • Copy the connection string. It will look something like this:

mongodb+srv://<username>:<password>@cluster0.mongodb.net/libraryDB?retryWrites=true&w=majority

8. Update Your server .env File:
   • In your server directory, create a .env file if it doesn't already exist.
   • Add your MongoDB connection string to the .env file as your MONGO_URI.

Testing the Connection

1. Start the Server:

• Navigate to the server directory:

cd server

• Start the server:

npm run dev

• Verify Connection: Check the terminal for a message indicating a successful connection to MongoDB.

By following these steps, you will have a MongoDB Atlas database set up and connected to your MERN stack application.

Environment Variables

Environment variables are used to configure your application without hardcoding sensitive information into your code. For this project, you need to set up the following environment variables in a .env file located both in the server directory and client directory:

Setup Server .env file

The server .env file should contain the following environment variables:

1. MONGO_URI: This variable contains the connection string for your MongoDB database. It tells your server where to find the database and how to connect to it. You will get this connection string from MongoDB Atlas when you set up your database.

2. PORT: This variable defines the port on which your Express server will run. By default, this is set to 5000, but you can change it to any available port number.

How to Set Up Your .env Server File

1. Create a .env File:
   • Navigate to the server directory:

cd server

• Create a file named .env if it does not already exist.

2. Add the Environment Variables:
   • Open the .env file in a text editor.
   • Add the following lines, replacing placeholders with your actual values:

MONGO_URI=mongodb+srv://<username>:<password>@cluster0.mongodb.net/libraryDB?retryWrites=true&w=majority
CLIENT_URL=http://localhost:3000
PORT=5000

• Replace MONGO_URI to be your created Atlas DB connaction string
• You can change 5000 to any port number you prefer.
• Make sure CLIENT_URL is set to your client current port.

Setup Client .env file

The client .env file should contain the following environment variables:

1. REACT_APP_API_URL: This variable contains the URL of your backend API. It tells your client where to send requests to interact with the server. By default, this should be set to http://localhost:5000/api, but you should change it to match your server's actual URL if different.

How to Set Up Your .env Client File

1. Create a .env File:
   • Navigate to the client directory:

cd client

• Create a file named .env if it does not already exist.

2. Add the Environment Variables:
   • Open the .env file in a text editor.
   • Add the following line, replacing the placeholder with your actual server URL:

REACT_APP_API_URL=http://localhost:5000/api

Replace http://localhost:5000/api with the URL of your backend server if it is running on a different host or port.

Usage

This section explains how to use the application once it’s set up and running. Follow these steps to interact with both the client and server components of the application.

Running the Server

1. Navigate to the Server Directory:
   • Open a terminal and change to the server directory:

cd server

2. Start the Server:
   • Start the Express server in development mode:

npm run dev

• By default, the server will run on http://localhost:5000. You can change the port by modifying the PORT variable in your .env file.

3. Verify Server Operation:
   • Open a browser or API client (like Postman) to test your API endpoints.

Running the Client

1. Navigate to the Client Directory:
   • Open a new terminal window or tab and change to the client directory:

cd client

2. Start the Client:
   • Start the React development server:

npm start

• By default, the client will be accessible at http://localhost:3000.

3. View the Application:
   • Open a web browser and navigate to http://localhost:3000 to view the application. The client communicates with the backend server to fetch and display data.

Stopping the Servers

• Stop the Express Server:

  • In the terminal where the server is running, press Ctrl + C to stop the server.

• Stop the React Client:

  • In the terminal where the client is running, press Ctrl + C to stop the client.

Troubleshooting

• Server Issues:

  • Check the terminal for error messages and ensure your .env file is correctly configured.
  • Verify that MongoDB Atlas is running and accessible.

• Client Issues:

  • Ensure that the React development server is running and that you have no conflicting applications using port 3000.
  • Check the browser console for errors if the client is not displaying correctly.

By following these steps, you should be able to run and interact with both the client and server components of the application effectively. If you encounter issues, refer to the troubleshooting tips or consult the documentation for more detailed guidance.

Best Practices for Implementing a Full Stack Feature

When working with a full-stack application, especially in a collaborative environment, it's crucial to follow best practices to ensure smooth development and maintainability. Here are the steps and practices to implement a new feature effectively in this project:

1. Understand the Feature Requirements
   • Review the Requirements: Carefully read the product requirements document to understand the feature's goals and user interactions.
   • User Stories: Refer to user stories to get a clear picture of the user workflows and interactions needed for the feature.
2. Plan the Database Schema
   • Identify Entities: Determine the new entities required for your feature and how they relate to existing ones.
   • Design Schema: Design the database schema, avoid redundant fields.
3. Implement Server-Side Logic
   • API Endpoints: Define the necessary API endpoints following RESTful principles.
   • Controllers: Implement controller functions to handle business logic, ensuring they are modular and reusable.
   • Validation: Implement validation for incoming data to ensure it meets required criteria.
   • Error Handling: Ensure proper error handling and logging to manage and log errors gracefully.
4. Develop Client-Side Logic
   • Routing: Set up routing using the library React Router to manage navigation.
   • Components: Break down the UI into reusable components, each with a single responsibility.
   • State Management: Use the React state and Context (state management solution implemented in this project) to manage application state.
   • API Integration: Implement a service layer for API calls, keeping API logic separate from UI logic.
5. Integrate Client and Server
   • Configure Axios: make sure Axios is set with a base instance that includes the base URL and default headers for API calls.
   • Process Responses: Handle server responses and update the UI accordingly, managing loading states and errors.
6. Testing (optional here but a must in real life production)
   • Unit Tests: Write unit tests for individual components, controllers, and models.
   • Integration Tests: Ensure that different components work together correctly through integration tests.
   • End-to-End Tests: Simulate user interactions with end-to-end tests to ensure the entire feature works as expected.
7. Deployment and Monitoring (optional here but a must in real life production)

Team Synchronization

• Regular Meetings: Hold regular meetings to discuss progress, blockers, and next steps. Daily stand-ups and weekly sync meetings can help keep everyone on the same page.
• Code Reviews: Conduct code reviews to ensure code quality and share knowledge among team members.
• Branch Management: Use a branching strategy with Git to manage feature development and integration.
• Documentation: Keep documentation updated to reflect changes and new features. This includes the README, API documentation, and any internal wiki pages.
• Clear Communication: Maintain clear communication channels (e.g., Slack, Teams) for quick discussions and updates.

Example Workflow

• Requirement: Implement a "Create New Duck" feature where users can add a new duck to the library.
• Database Schema: Add a ducks collection with fields like name, description, image url.
• API Endpoint: Create a POST /api/ducks endpoint to handle new duck creation.
• Controller Logic: Implement the createDuck controller to validate and save the duck to the database.
• Client Component: Create a NewDuckForm component with form fields and a submit button.
• State Management: Use React state to manage form inputs and submission status.
• API Call: Use Axios in the NewDuckForm to send a POST request to POST /api/ducks.
• Testing: Write tests for the NewDuckForm component, createDuck controller, and the API endpoint.

By following these best practices, you can ensure that each feature in your full-stack application is well-designed, maintainable, and scalable. This approach will help you efficiently extend the existing infrastructure while adhering to the project requirements.

Project Structure

• client/: Contains the React frontend application.
• server/: Contains the Express backend application, including API routes and database models.

queenb-summer-project-template-24/
│
├── client/                 # React client
│   ├── public/
│   └── src/
│       ├── components/
│       ├── pages/
│       ├── services/
│       ├── styles/
│       ├── App.js
│       ├── index.js
│       └── package.json    # Client dependencies
│
├── server/                 # Node.js server
│   ├── controllers/
│   ├── models/
│   ├── routes/
│   ├── .env                # Environment variables
│   ├── server.js           # Main server file
│   └── package.json        # Server dependencies
│
├── README.md
└── package.json            # Root package.json for repo management

Explanation

Root Directory

• queenb-summer-project-template-24/: This is the root directory of your project.

Client Directory

• client/: Contains the React frontend application.
  • public/: Static files like index.html, images, and other assets that need to be served directly.
  • src/: Contains the source code for the React application.
    • components/: Reusable UI components such as buttons, forms, and other elements.
    • pages/: Page components that represent different routes in the application.
    • services/: Services for making API calls and handling business logic.
    • styles/: CSS and styling files for the application.
    • App.js: The main React component that sets up routing and renders the application.
    • index.js: The entry point for the React application, responsible for rendering the App component into the DOM.
    • package.json: Lists the client-side dependencies and scripts for managing the React application.

Server Directory

• server/: Contains the Node.js backend application.
  • controllers/: Contains the logic for handling API requests and responses.
  • models/: Mongoose models that define the data schema for MongoDB.
  • routes/: Defines the API endpoints and maps them to controller functions.
  • .env: Stores environment variables like database connection strings and server port.
  • server.js: The main server file that sets up Express, connects to the database, and starts the server.
  • package.json: Lists the server-side dependencies and scripts for managing the Node.js application.

Additional Files

• README.md: Provides documentation for the project, including setup instructions, usage, and other relevant information.

Summary

The provided setup instructions cover the installation, configuration, and running of both the client and server, including setting up environment variables and connecting to MongoDB Atlas. By following the guidelines, you will be able to develop a complete application and understand the key components of a full-stack web development project.

Feel free to customize and extend this template based on your project requirements and learnings from the mentorship program.

For any issues please contact us via mail or open an issue.

Happy Coding! :)