sushilparajuli / MERN-Stack-Blog

Complete Blog site with server-client authentication developed on MERN STACK

React Blog (MERN-STACK)

Server Side (server folder)

Express, Mongodb, Mongoose are used to built the server. Please view package.json file for to deep dive into the packages used for it

Some note: You have to create data/db folder inside the server/ folder for mongo db (after successfully installing mongodb) and have to take ownership of the folder

• Command for linx/Mac to take ownership

  sudo chmod -R $USER data/db

• Windows user follow here

And for the secret text, please put secret text in the config.js file

module.exports={ secret: ' secret text here ' }

Command to run Server

• First, run mongod from server/
• Then, run nodemon seperately within server/

Client Side (client folder)

This is client app of the react blog app

This project was bootstrapped with Create React App.

Below you will find some information on how to perform common tasks.
You can find the most recent version of this guide here.

Folder Structure

After creation, your project should look like this:

my-app/
  README.md
  node_modules/
  package.json
  actions/
  public/
    index.html
    favicon.ico
  reducers/
  src/
    auth/ 
      Comoponents related to authentication
    App.css
    App.js
    App.test.js
    index.css
    index.js
    posts_index.js
    posts_new.js
    posts_show.js
    404.js

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Supported Language Features and Polyfills

This project supports a superset of the latest JavaScript standard.
In addition to ES6 syntax features, it also supports:

• Exponentiation Operator (ES2016).
• Async/await (ES2017).
• Object Rest/Spread Properties (stage 3 proposal).
• Dynamic import() (stage 3 proposal)
• Class Fields and Static Properties (stage 2 proposal).
• JSX and Flow syntax.

Learn more about different proposal stages.

While we recommend to use experimental proposals with some caution, Facebook heavily uses these features in the product code, so we intend to provide codemods if any of these proposals change in the future.

Note that the project only includes a few ES6 polyfills:

• Object.assign() via object-assign.
• Promise via promise.
• fetch() via whatwg-fetch.

If you use any other ES6+ features that need runtime support (such as Array.from() or Symbol), make sure you are including the appropriate polyfills manually, or that the browsers you are targeting already support them.