Mandatory driver instruction and certification LMS for all civilian and commercial heavy-machinery license applicants across Egypt. Operated entirely within a state intranet with zero internet connectivity by security mandate. No external package repositories, no remote access, no developer presence on-site during operation. System had to be self-sufficient, fault-tolerant, and executable by non-technical ministry personnel holding high-level security clearance.

//Engineering Impact

• ->Engineered a zero-network deployment pipeline by custom-patching Oracle Linux 7.6 to use a physical USB drive as a localized package repository — eliminating all external network dependencies from the installation and upgrade lifecycle.
• ->Authored fault-tolerant Bash automation scripts enabling non-technical ministry personnel with high-level security clearance to execute complex multi-branch Git merges, schema migrations, and configuration state updates — without developer access, without network connectivity, and without failure tolerance for error.
• ->Designed iconography-driven UX flows to serve a demographically diverse user base with significant literacy variance, while maintaining strict compliance with legal testing mandates.
• ->Implemented offline billing voucher generation operating entirely within the air-gapped environment, with no external payment network dependencies.

//Edge Cases Managed

• ->Absolute network isolation: all package management, version control operations, and schema migrations had to execute without any internet or intranet gateway access.
• ->Operator constraint: on-site personnel had security clearance but zero technical background — upgrade scripts had to be deterministic, self-validating, and recoverable without developer intervention.
• ->PHP 7.0.33 constraint: legacy runtime imposed by the ministry's locked infrastructure — all development had to remain within that version's boundaries regardless of upstream Moodle requirements.
• ->Multi-branch Git operations in an offline environment — standard Git workflows assume network access for remote operations; all merge and deployment logic had to be pre-packaged and locally executable.