mirrorcentral

Python FastAPI backend for Mirror, a Kotlin Android makeup simulation app. This service backs the Pro/business tier: it accepts a captured photo plus the makeup look applied to it, runs a higher-quality server-side render (and, later, an AI-assisted polish pass), and returns the enhanced image. It also owns user accounts, client/look data, and subscription entitlements.

Status: phase 1 of 8 — project scaffolding, config loading, database models, the initial Alembic migration, and a /health check. Auth, CRUD, the enhance pipeline, entitlements, and deployment tooling land in subsequent phases; this README will grow into full setup/deploy docs at that point.

Also included, ahead of the phased build order: a server-rendered admin console at /admin (Mirror staff only — separate session-cookie auth from the mobile app's JWT auth) covering users, subscriptions, enhance jobs, the shade library, client/look lookup, and an audit log of every admin action. See Admin console below.

Tech stack

• Python 3.12, FastAPI, Pydantic v2, pydantic-settings for config
• SQLAlchemy 2.0 (async) + SQLModel + Alembic for migrations
• Postgres (Neon), read from DATABASE_URL
• Redis + arq for the background enhance job queue
• boto3 / Cloudflare R2 for photo storage
• JWT auth, passlib/bcrypt for password hashing
• httpx for outbound calls (AI provider, Paystack)

Local setup (phase 1)

python -m venv .venv
./.venv/Scripts/activate       # Windows
pip install -e ".[dev]"
cp .env.example .env           # then fill in DATABASE_URL and JWT_SECRET at minimum
alembic upgrade head
uvicorn app.main:app --reload

Run tests with:

pytest

Admin console

A server-rendered console for Mirror staff at /admin, built with Jinja2 templates (no separate frontend build/deploy). Authenticated via a signed session cookie — entirely separate from the mobile app's JWT auth — with three roles:

• owner — everything, plus managing other admin accounts
• support — day-to-day operations (edit subscriptions, retry jobs, manage shades)
• viewer — read-only

Covers: dashboard (usage/health metrics), users, subscriptions, enhance jobs (with retry), the shade library (CRUD), client/look lookup (read-only), and an append-only audit log of every state-changing admin action.

There's no self-service admin signup by design. Create the first (owner) account with:

python scripts/create_admin.py [email protected] --role owner