- Backend: FastAPI app with all models, services, schemas, routes - Admin Panel: Next.js dashboard with all modules (CRM, POS, repairs, warranties, billing, notifications, etc.) - Ecommerce: storefront (submodule) + product catalog - AI Agents: .agents/ skill library for Antigravity IDE - Docs: architecture, billing, notification gateway markdown - Submodules: Backend/OpenWA, Ecommerce/File 2/storefront
1 KiB
1 KiB
| name | description |
|---|---|
| MySQL Migration Safety | Ensures database schema migrations are safe, non-blocking, and backwards-compatible. |
Skill: MySQL Migration Safety
1. Purpose
Avoid database downtime, long table locks, or transactional data loss when applying migrations using Alembic in production.
2. When to Use
Before generating or applying Alembic database migration scripts.
3. Step-by-Step Checklist
- Backward Compatibility: Ensure new columns are added as nullable or with a default value.
- Table Locking Check: Avoid adding indexes or modifying column types directly on large tables (e.g. over 100k rows) during peak hours. Use online schema change patterns if necessary.
- Data Migrations: Separate schema changes (DDL) from data transformation changes (DML) into distinct migration steps.
- Rollback Script: Ensure
downgrade()in Alembic is fully implemented and tested. - Alembic History: Run
alembic historyto confirm there are no branching version conflicts.