After cloning, you need to install a few requirements make sure you have the following installed
- Node.js : The JavaScript runtime
- Yarn: A package and project manager for Node.js applications
- Python: A recent Python 3 interpreter to run Flask backend
- install missing packages
foo@bar:~/../Twitter-Topic-Tracking$ yarn
foo@bar:~/../Twitter-Topic-Tracking$ yarn install react-spring- create virtual environment Unix-bas
foo@bar:~/../Twitter-Topic-Tracking$ cd api
foo@bar:~/../Twitter-Topic-Tracking/api$ python3 -m venv venv
foo@bar:~/../Twitter-Topic-Tracking/api$ source venv/bin/activate
(venv) $ _Windows
foo@bar:~/../Twitter-Topic-Tracking$ cd api
foo@bar:~/../Twitter-Topic-Tracking/api$ python -m venv venv
foo@bar:~/../Twitter-Topic-Tracking/api$ venv\Scripts\activate
(venv) $ _- install missing modules
(venv) foo@bar:~/../Twitter-Topic-Tracking/api$ pip install -r requirements.txtYou will need to open 2 terminal windows
- start flask backend terminal window
(venv) foo@bar:~/../Twitter-Topic-Tracking/api$ cd ..
windows
(venv) foo@bar:~/../Twitter-Topic-Tracking/$ yarn start-api-windows
linux
(venv) foo@bar:~/../Twitter-Topic-Tracking/$ yarn start-api-linux- start react frontend
(venv) foo@bar:~/../Twitter-Topic-Tracking/$ yarn startThe yarn start and yarn start-api commands are described below
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the react frontend 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.
proxy is added that points to [http://localhost:5000]
This is for any commands the frontend doesn't understand
They will be forwarded to the backend
Runs the flask backend in the development mode.
run on [http://localhost:5000]
The page will reload if you make edits.\
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
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.
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify