Nachovoss Hatchback Hatchback

Hatchback Project Skill

This project was generated with Hatchback — a production-ready FastAPI boilerplate with SQLAlchemy 2, Alembic migrations, JWT auth, multi-tenancy, and Docker support.

Architecture Overview

The project follows a clean architecture pattern with four distinct layers:

app/
├── models/          # SQLAlchemy ORM models (DB layer)
├── repositories/    # Data access — wraps queries, extends BaseRepository
├── services/        # Business logic — orchestrates repositories
├── routes/          # HTTP endpoints — thin controllers, delegates to services
├── schemas/         # Pydantic v2 request/response schemas
├── config/          # Database connection, rate limiter, settings
├── dependencies.py  # FastAPI dependency injection (auth, services)

Data flow: Route → Service → Repository → Model

Key Conventions

1. Resource naming: always snake_case (e.g. blog_post). The CLI and templates derive PascalCase class names automatically (BlogPost).
2. Primary keys: UUID columns via sqlalchemy.dialects.postgresql.UUID(as_uuid=True).
3. Schemas: use Pydantic v2 (model_dump(), not .dict()). Every resource should have Create, Update, and Response schemas in app/schemas/<resource>.py.
4. Repositories extend app/repositories/base.py (BaseRepository) which provides get_all, get_by_id, create, update, delete.
5. Routes use FastAPI Depends() for DB sessions and service injection.
6. Registering new resources: imports must be added to:
   • app/models/__init__.py
   • app/routes/__init__.py (add to routers list)
   • app/services/__init__.py (add to __all__)
   • app/repositories/__init__.py (add to __all__)

Hatchback CLI Commands

Run these from the project root (where requirements.txt lives). hbk is a shorthand alias — hbk make product is equivalent to hatchback make product.

Scaffolding a new resource

hatchback make product

This creates:

• app/models/product.py — SQLAlchemy model
• app/schemas/product.py — Pydantic schemas (Create, Update, Response)
• app/repositories/product.py — Repository extending BaseRepository
• app/services/product.py — Service with CRUD methods
• app/routes/product.py — Full REST router (GET, POST, PUT, DELETE)
• tests/test_products.py — Pytest stubs

It also auto-updates the __init__.py files in models, routes, services, and repositories.

Removing a resource

hatchback remove product        # asks for confirmation
hatchback remove product --force # skips confirmation

This deletes all 6 files created by make and removes the corresponding imports from all __init__.py files.

Database & Migrations

• Engine: PostgreSQL via psycopg2-binary
• ORM: SQLAlchemy 2 with synchronous sessions
• Config: app/config/database.py reads from .env (see .env.example)
• Migrations: Alembic, configured in alembic.ini and alembic/

After modifying a model, always run:

hatchback migrate create -m "describe change"
hatchback migrate apply

Authentication & Multi-tenancy

• JWT tokens via python-jose[cryptography]
• Password hashing via passlib[bcrypt]
• Multi-tenant: every user belongs to a Tenant; tokens include tenant_id
• Auth dependencies in app/dependencies.py:
  • get_current_user — validates JWT, returns user
  • get_current_active_user — checks user status is "active"
  • RoleChecker(["admin"]) — role-based access control

Testing

• Framework: pytest with httpx (AsyncClient or TestClient)
• Config: tests/conftest.py sets up test DB session and fixtures
• Run: hatchback test

Environment Variables

See .env.example for required vars:

• DATABASE_USERNAME, DATABASE_PASSWORD, DATABASE_HOSTNAME, DATABASE_PORT, DATABASE_NAME
• SECRET_KEY — JWT signing key (auto-generated on hatchback init)
• MAILERSEND_API_KEY, MAILERSEND_FROM_EMAIL, MAILERSEND_FROM_NAME

Docker

• Dockerfile — Python slim image, installs requirements, runs Uvicorn
• docker-compose.yml — App + PostgreSQL service
• Start DB only: docker-compose up -d db

Converted and distributed by TomeVault — claim your Tome and manage your conversions.