eCommerce platform built with MERN stack (MongoDB, ExpressJS, ReactJS, Nodejs)
- Table of Contents
- Demo videos
- Purpose
- Project URL:
- Features
- Usage
- Project Layout
- Testing
- Future implementations
- Roles
- Deployment
- License
The purpose of the application is to provide an e-commerce platform for consumers and vendors to buy & sell products. It takes inspiration on modern applications like eBay or Amazon. Data sources are self-generated, but they conform to some schema from Amazon products datasets [1], [2], [3].
https://comp3120-shopology.herokuapp.com
- Full featured shopping cart
- Product reviews and rating
- Top products carousel
- Instant search for any product with Algolia search engine
- User profile with orders
- Seller profiles with products
- Admin products, orders, users management
- Checkout process
- PayPal/ credit cart integration
- User/Seller account elevation
Create a .env file in the root and add the following
NODE_ENV = development
PORT = 3001
MONGO_URL = your mongodb uri
JWT_SECRET = set your secret key for JWT token
PAYPAL_CLIENT_ID = your paypal client id
ALGOLIA_APP_ID = your algolia application API
ALGOLIA_API_KEY = your algolia admin api
Create a .env file in the client/ folder
SKIP_PREFLIGHT_CHECK=true
npm install
cd client
npm install
# Run frontend (:3000) & backend (:3001)
npm run dev
# Run backend only (with nodemon)
npm run server
# Run backend only (without nodemon)
npm run server
# Run frontend only
npm run client
# Test
npm run test
Note: for seeding the data, you should destroy data first then import them.
You can use the following commands to seed the database with some sample users and products as well as destroy all data
# Import data
npm run data:import
# Destroy data
npm run data:destroy
Sample User logins
ahihi@test.com (Admin)
123456
ahihi2@test.com (Customer)
123456
ahihi3@test.com (Customer)
123456
src/ Root directory of react app
├── App.js Layout of the whole application
├── App.test.js Testing for the application
├── actions/ Store the action of global store(Redux)
├── components/ Store all the re-usable components
├── constants/ Store the constants for all the reducers(Redux)
├── index.css Apply global styling
├── index.js Main entry point for the application
├── media/ Store logo
├── reducers/ Reducers for global state(Redux)
├── screens/ Multiple screens for each main link in (react-router)
│ ├── Auth/ Authentication screen (login, register,etc)
│ ├── CartScreen/ Cart page
│ ├── HomeScreen/ Home page
│ ├── OrderScreen/ Order page
│ ├── PaymentScreen/ Payment page
│ ├── PlaceOrderScreen/ PlaceOrder page
│ ├── ProductScreen/ Product page
│ ├── Profile/ Profile page
│ │ ├── Admin/ Admin Screen page
│ │ └── User/ User Screen page
│ └── Shipping/
├── setupTests.js/ Set up test for frontend
└── store.js Main store for global state(Redux)
backend/
├── app.js Main entry for REST API of the application
├── config/ Config folder (currently, only setup for database)
├── controller/ Main logic of the API
├── data/ Testing data
├── middlewares/ Middlewares
│ ├── authMiddleware.js Middlewares for checking token
│ └── errorHandlers.js Middlewares for handling any errors
├── model/ Model data for mongodb
├── routes/ All the main routes of the API
├── seeder.js Script for auto import and destroy the data (testing purpose only)
├── server.js Run the server
├── test/ All the tests for API
├── uploads/ Static folder contains all the image
└── utils/ Contain all re-usable functions
└── generateToken.js Currently, only having function for generate JWT tokens
npm run test
After running the script, you will get a coverage folder that contains details about all the test case as well as the percentage of coverage for the API.
You can open the file coverage/lcov-report/index.html to have better visualization.
- Recommendation system for shoppers
- Social login using third-party vendors like Google, Facebook
- Van Nguyen Nguyen - front end developer
- Sujith Bellam - front end developer
- Sepehr Torfeh Nejad - back end developer
- Canh Thanh Nguyen - back end developer
- Communications and collaboration:
i. The team had weekly meetings to discuss features to implement, and go over presentation for sprints
ii. Pull requests are reviewed by at least 1 other team member. Merge conflicts are promptly resolved.
MIT License
Copyright (c) 2021
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.