Future Plans:
- A place to add parts and inventory to location really fast. A part PUT request, then inventory PUT.
- A place to add part to repair's parts backref.
- A place to add repairs to part's repair_list.
- When a part is added to a repair, but is already in the DB, then it must be queried and added to that repair's part backref instead.
- A place to see all parts with empty repair_list, then option to select repairs to add.
- Analyses page to see all parts with inventories and the repairs for them.
- A repairs page with all inventories below 4 or missing inventory.
- Logon system
- Posgresql or mysql
- email alerts when new parts added to inventory.
Set up API first
Before using the front end application we need to set up our backend, which handles our API. It's written in python3 using the Flask microframework. The chromebook parts data was stored in a simple json that gets passed to the react built front end, but now the data is stored in a SQLite database, which is included!
Create Virtual Environment for python
cd ./api
python3 -m venv venv
Activate virtual environment
source ./venv/bin/activate
Install dependencies from requirments.txt
pip install -r requirements.txt
Setup your .env files in ./api.api and .api.api/data
FLASK_DB="" //Remember database is included, so this isn't much of a secret! It will be in the future though, when inventory is added!
Run Flask API on localserver
flask run
or
cd ..
npm run api
Run react development server
cd .. (if you're still in ./api directory)
npm run start
Extra React.js information:
Getting Started with Create React App
This project was bootstrapped with Create React App.
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.
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