This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
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
To set up and run the project, you’ll need:
- Python 3.6+ and pip
- PostgreSQL and pgAdmin (for database management)
- Git for cloning the repository
- Flask CLI (comes with Flask installation)
git clone [email protected]:ameliazhengg/FinTrack.git
cd FinTrackCreate a .env file in the backend directory with the following variables:
DATABASE_URI=postgresql+psycopg2://<YOUR_USER>:<YOUR_PASSWORD>@db:5432/<DATABASE_NAME>
POSTGRES_USER=<YOUR_USER>
POSTGRES_PASSWORD=<YOUR_PASSWORD>
POSTGRES_DB=<DATABASE_NAME>REPLACE <YOUR_USER> with your desired PostgreSQL user.
REPLACE <YOUR_PASSWORD> with your PostgreSQL password.
REPLACE <DATABASE_NAME> with your database name (FinTrack is preferred).
- For SWEs: DO NOT PUSH THIS TO GITHUB, it is already specified in
.gitignore. MAKE SURE YOU NEVER PUSH THIS FILE!
Run the following command from the project root to build and start the backend and database services:
docker-compose up --buildThis command will:
- Build the Docker image for the backend.
- Spin up a container for the Flask API and another for the PostgreSQL database.
The Flask API should now be running at http://127.0.0.1:5005.
To set up the database tables inside the running container, run the following command:
docker exec -it backend_flask_app flask db upgradeThis command will apply the initial database migrations.
- Note, if there isn't already a
migrationsfolder in the repo (there will be), run:
docker exec -it backend_flask_app flask db initbefore running flask db upgrade.
cd ../frontendnpm installnpm startThe React app should now be running at http://localhost:3000 and will automatically connect to the Flask backend.
Migrations are a way to version-control database schema changes. They allow us to manage incremental updates to the database structure safely and avoid issues such as data loss. This process is essential for ensuring that changes to models.py reflect in the database without having to drop tables or recreate data from scratch.
Migrations use a combination of Python scripts and database commands to apply changes to your database tables based on changes made to the models in models.py. Flask-Migrate, which leverages SQLAlchemy, allows us to manage these changes seamlessly.
When you make changes to models.py, such as adding or altering columns, generate a new migration script with:
flask db migrate -m "describe your changes here"This command will create a migration file in the migrations/versions directory. Review this file to ensure it captures the intended changes.
Once the migration script is created and reviewed, apply it to the database with:
flask db upgradeThis command will update the database schema based on the migration script without deleting existing tables or data.
If an applied migration introduces issues, you can revert the last migration using:
flask db downgradeThis command rolls back the most recent migration, undoing the changes it introduced. Use this cautiously, as it will remove any schema modifications from the latest migration. Rolling back should only be done when necessary, and ideally, migrations should be thoroughly reviewed and tested before upgrading.
Modify the models by adding, altering, or removing fields as needed for the database schema.
Run the following command to create a migration script that reflects your changes:
flask db migrate -m "describe your changes"This will generate a new migration file in the migrations/versions directory, capturing the intended changes to the schema.
Check the generated migration file to confirm it accurately reflects the changes made in models.py. Ensure no unintended alterations are present.
Run flask db upgrade to apply the migration to the database schema. This step should be done once you are confident that the migration script is accurate.
After applying the migration, test the database and application to verify that the changes were successful and did not introduce any issues.
If any errors occur after a migration, use flask db downgrade to revert the changes. Make further adjustments as needed and repeat the process from Step 2.