Skip to content

HemangiS/twitter-react-node

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

twitter-react-node

twitter website built using React, Node.js, PostgreSQL and Express.

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.

Table of Contents

Prerequisites

Folder Structure

After creation, your project should look like this:


twitter-react-node/
  README.md
  backend/
    helpers/
      db.js
    public/
      css/
        style.css
      images/
        cover.jpg
      js/
        twitter.js
    routes/
      index.js
    test/
      index.js
    views/
    app.js
    example.env
    script.sql
    scripttest.sql
    package.json
    Readme.md
  frontend/
    public/
      css/
        style.css
      images/
        cover.jpg
        logo.png
      fevicon.ico
      index.html
    src/
      components/
        about.js
        App1.js
        App2.js
        AppRoutes.js
        deletetweet.js
        editprofile.js
        follow.js
        followers.js
        index1.js
        login.js
        logout.js
        profile.js
        register.js
        tweet.js
        unfollow.js
        welcome.js
        yourprofile.js
      App.css
      App.js
      App.test.js
      index.css
      index.js
      logo.svg
      routes.js
    package.json
    README.md

For the project to build, these files must exist with exact filenames:

  • public/index.html is the page template;
  • src/index.js is the JavaScript entry point.

You can delete or rename the other files.

You may create subdirectories inside src. For faster rebuilds, only files inside src are processed by Webpack.
You need to put any JS and CSS files inside src, or Webpack won’t see them.

Only files inside public can be used from public/index.html.
Read instructions below for using assets from JavaScript and HTML.

You can, however, create more top-level directories.
They will not be included in the production build so you can use them for things like documentation.

Setup

In the frontend 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.

In the backend directory, you can run:

npm i

installs dependencies

node app

Runs the app in the development mode on port 8000.

Features

  • User Login using personal mail account.
  • User Self-registration form.
  • User's details are stored in their profile.
  • User can post their thoughts and updates using tweet feature.
  • User can follow other users to share thoughts and updates.
  • User can update their profile.
  • User can delete their tweets.
  • User can logout.

About

No description or website provided.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published