Skip to content

Rishav-Agarwal/abierto

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

21 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

abierto

Get honest feedback

How to use?

  1. Fork and Clone this repository.
  2. Move to the root directory of the project(> abierto).
  3. Run the command- npm install in your terminal.
  4. Create two files named .env. One in the client folder(> abierto/client) and other in the server folder(> abierto/server). It contains the private keys for the APIs used. The list of environment variables is listed below.
  5. To start the development server, run the command- npm run dev in your terminal.
  6. Open http://localhost:3000 to view it in the browser.

The .env file in abierto/client folder

REACT_APP_GOOGLE_SIGNIN_CLIENT_ID=YOUR_CLIENT_ID.apps.googleusercontent.com

The .env file in abierto/server folder

REACT_APP_GOOGLE_SIGNIN_CLIENT_ID=YOUR_CLIENT_ID.apps.googleusercontent.com
REACT_APP_MONGODB_URI=YOUR_MONGODB_SRV_STRING

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

npm run dev

Run the client@3000 port in development mode and the server@5000 port.
Open http://localhost:3000 to view the app in the browser.

The client and server will reload if you make any changes.

npm run client

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 run server

Run the server locally on 5000 port.

The server will restart automatically if you make any edits.

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.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

npm run build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify