MyLFA is a digital registration platform designed to simplify registration for the Lebanon Football Association (LFA). It provides a centralized entry point for football academies, players, coaches, and administrators.

The platform brings key onboarding workflows into one digital experience, helping reduce fragmented records and manual registration processes. Alongside the registration platform, I completed PostgreSQL migration and production-readiness work with Omar Masri to safely align the production environment with development.

The platform needed clear registration paths for multiple football stakeholders while maintaining a secure and reliable database foundation.

The production database operated under managed-platform restrictions, including a non-superuser environment and limited automated deployment support. Any migration work had to preserve existing security controls, database ownership behavior, Prisma migration history, and production data.

MyLFA presents users with a focused registration interface and distinct onboarding paths for each role:

Academy registration

Player registration

Coach registration

Administrator registration

Sign-in for existing users

Club registration, planned as a future expansion

Behind the product experience, I designed and validated a controlled database migration process that supported safe schema deployment without touching live production data during testing.

I conducted read-only audits of both development and production PostgreSQL environments, mapping the schema and security model before proposing changes.

The work included:

Auditing 300+ tables, 600+ RLS policies, 180+ SECURITY DEFINER functions, and 288 triggers

Reviewing roles, grants, ownership behavior, and row-level security configurations

Identifying missing RLS predicates, functions, and triggers omitted by automated publishing

Building isolated shadow databases that matched production restrictions

Running safe schema deployment dry-runs without making changes to live data

Achieving full schema parity between development and production

Baselining Prisma migrations while preserving _prisma_migrations history and leaving historical migration files unchanged

Documenting necessary platform deviations, including object ownership differences, and verifying that RLS and security behavior remained intact

Creating transactional forward-migration plans to install missing security objects without weakening the existing security contract

PostgreSQL

Prisma migrations

Row-Level Security, including FORCE RLS

SECURITY DEFINER functions

Database triggers

Roles, grants, and ownership

Shadow databases

Schema parity testing

Controlled production deployment

The migration work established a safe, traceable path to bring the production database into parity with development while preserving the platform’s security model and migration integrity.

This gave the MyLFA platform a more reliable foundation for managing registration data as the product expands across academies, players, coaches, administrators, and future club workflows.