BizTracker Lead Generator Development

Portfolio project

BizTracker Lead Generator

A comprehensive lead generation and management system for service-based businesses.

Project Structure

biz_Tracker_lead_generator/
├── .github/          # GitHub configurations and hooks
├── backend/          # FastAPI backend
├── frontend/         # Expo React native

GitFlow Workflow

We follow the GitFlow branching model for development:

Main Branches

main - Production-ready code

develop - Latest development changes

Supporting Branches

feature/* - New features

release/* - Release preparation

hotfix/* - Urgent production fixes

bugfix/* - Bug fixes for the develop branch

Branch Naming Convention

Features: feature/feature-name

Bugs: bugfix/bug-description

Hotfixes: hotfix/issue-description

Releases: release/version-number

Workflow Rules

Development Flow:

All development happens in feature branches

Feature branches are created from develop

Feature branches are merged back into develop via Pull Request

Code review is required before merging

Release Process:

Release branches are created from develop

Only bug fixes and release preparations in release branches

Release branches are merged into main AND develop

Tag the release in main with version number

Delete release branch after merging

Hotfix Process:

Hotfix branches are created from main

Only critical bug fixes in hotfix branches

Hotfix branches are merged into main AND develop

Tag the hotfix in main with updated version number

Delete hotfix branch after merging

Pull Request Requirements:

All code changes require a Pull Request

PRs must be reviewed by at least one team member

All tests must pass

No sensitive data in commits

Follow commit message convention

Version Tagging:

Releases: v1.0.0, v1.1.0, etc.

Hotfixes: v1.0.1, v1.1.1, etc.

Use semantic versioning (MAJOR.MINOR.PATCH)

Commit Message Convention

type(scope): subject

[optional body]

[optional footer]

Types:

feat: New feature

fix: Bug fix

docs: Documentation

style: Formatting

refactor: Code restructuring

test: Adding tests

chore: Maintenance

Example: feat(auth): implement JWT authentication

Getting Started

Prerequisites

Python 3.8+

PostgreSQL

Redis

Setup

Clone the repository

git clone [repository-url]
cd biz_Tracker_lead_generator

Set up Git hooks (Important!)

# Create symbolic link to the pre-commit hook
ln -sf ../../.github/hooks/pre-commit .git/hooks/pre-commit
# Make the hook executable
chmod +x .git/hooks/pre-commit

Create and activate virtual environment

python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate

Install dependencies

cd backend
pip install -r requirements.txt

Set up environment variables

cp .env.example .env
# Edit .env with your configurations

Initialize the database

# Coming soon

Development Workflow

Create a new feature branch

git checkout develop
git pull origin develop
git checkout -b feature/your-feature-name

Make your changes and commit

git add .
git commit -m "feat(scope): description"

Push your changes

git push origin feature/your-feature-name

Create a Pull Request to the develop branch

License

[License Type] - See LICENSE file for details

Security Practices

Environment Variables

Never commit .env or .env.docker files

Use .env.example and .env.docker.example as templates

Copy example files and fill in your own values:

Pre-commit Hook

The repository includes a pre-commit hook that:

Prevents committing sensitive files

Checks for potential credentials in code

Can be bypassed with git commit --no-verify if needed

Sensitive Information

Never commit API keys, passwords, or tokens

Use environment variables for sensitive data

Keep credentials in .env files (not tracked by git)

Use secret management in production

0 likes · 7 views · Apr 21, 2025

Building a lead gen system for service businesses using FastAPI, Redis, and React Native to automate lead capture, filtering, and CRM pipeline integration.