Inherited Laravel marketplace with no documentation and a dead deploy

Two-sided marketplace · Laravel 6 · PHP 7.4 · jQuery · manual FTP deploys

The original developer had left, nobody could run the project locally, and the only deployment path was copying files onto the server by hand. The owner was afraid to change anything because a failed deploy meant downtime with no rollback.

The application can be cloned, booted and deployed by any Laravel developer from the README, and the owner has a prioritised list of what was deliberately left out of scope.

• Read the two-sided marketplace write-up
• Laravel Application Rescue

Stepwise upgrade off an unsupported Laravel and PHP release

B2B services company · Laravel 8 · PHP 7.4 · two abandoned Composer packages

The stack no longer received security fixes, and a previous upgrade attempt had been abandoned halfway, leaving a stale branch nobody trusted to merge.

The application runs on a supported Laravel and PHP branch, with a rollback plan that was written before the cutover rather than improvised during it.

• Read the b2b services company write-up
• Laravel Upgrade Service

Spreadsheet-driven operations replaced by a Filament admin panel

Operations team · Laravel API · spreadsheets · direct SQL for edits

Staff were exporting data to spreadsheets to make routine changes, and non-technical edits were being applied by a developer running SQL against production.

Day-to-day record changes are made by the operations team in the panel, and production SQL is no longer part of a routine workflow.

• Read the operations team write-up
• Laravel Filament Development

Reporting screens that timed out under real data volume

SaaS product · Laravel · MySQL · synchronous report generation

Report pages that were fine on seed data timed out against production-sized tables, and the queue was being used for almost nothing.

Report generation runs on the queue with the slow query paths indexed and profiled, and the profiling method is documented so the team can repeat it.

• Read the saas product write-up
• Laravel Performance Optimization

Start with a written diagnosis

Every engagement above began with a read-only audit before a line of code changed. The same $299 Laravel Triage Audit is how new work starts.

• Laravel Triage Audit — $299
• Describe your application