This document provides instructions for setting up the app, our development workflow, and deployment guidelines.
The project is divided into three main components: Frontend, Backend, and Database. Instructions for setting up each component are available in their respective README files.
This project follows a Git Workflow. For reference, you can check this link, but the main idea is outlined below.
We use a branch-based development workflow. Please follow these guidelines when creating branches:
main
: The main branch represents the production-ready code.development
: The development branch is where feature branches are merged before going to production.- Feature branches: Create a feature branch for each new feature or bug fix. Name it descriptively, such as
feature/add-authentication
orbugfix/fix-broken-link
.
Follow these commit message guidelines:
- Use imperative verbs (e.g., "Add feature," "Fix bug," "Update documentation").
- Keep commits focused on a single task.
- Create a new branch for your feature or bug fix.
- Commit and push your changes to your branch.
- Open a pull request from your branch to the
develop
branch. - Ensure that your PR has a clear title and description.
- Request code review from team members.
- Avoid force pushing to shared branches (
main
,develop
) unless necessary. - Be mindful of the commit history; keep it clean and easy to follow.
- Use meaningful branch and commit messages.
- Communicate with team members to coordinate changes.
- Docker Desktop
TODO: Add deployment instructions here.