TL;DR
- Shipped a
composer sharecommand + reverse-proxy trust so a local Laravel app can be tested over a public HTTPS tunnel without mixed-content errors. - Built a self-serve onboarding flow: upload a spreadsheet, a wizard maps the columns and auto-builds a metric and a dashboard.
- Added a CRM intake pass: bulk contact import (paste/CSV/Excel) with duplicate detection + merge, web lead capture via UTM, and an activity timeline feeding a lead-scoring engine.
Busy day across four repos. Grouping by theme, not commit order.
Public tunnels for local apps
The standout (full write-up: cleaniquecoders/kickoff): sharing a local app over a Cloudflare/ngrok tunnel kept breaking on mixed content because php artisan serve is HTTP behind an HTTPS proxy. Fixes — trustProxies(at: '*') so X-Forwarded-Proto is honoured, plus pointing APP_URL/ASSET_URL at the tunnel URL. Bundled into one composer share command that restores .env on exit.
Self-serve data onboarding
Across an analytics app, the theme was killing setup anxiety. The win: an upload-to-dashboard wizard where you drop a spreadsheet and it does the rest.
| Step | What it does |
|---|---|
| Upload | Accept an .xlsx, show a raw-data preview |
| Map columns | Smart defaults + guidance; each value column becomes its own metric |
| Validate | Friendly errors for duplicate metric key / board slug instead of a DB exception |
| Build | Auto-create the metric + a starter dashboard from the mapping |
Two details I liked: auto-deriving a Title-Cased label from the column name, and shipping ~30 industry sample datasets so a new user can click "try an example" instead of hunting for a file.
CRM intake + lead scoring
On the CRM side: getting leads in and ranking them.
- Bulk import — paste, CSV, or Excel. Missing name? Derive a Title-Cased one from the email; keep existing app users out of the funnel; map Status/Type and Source columns.
- Web lead capture — a UTM-aware intake endpoint with duplicate detection and a merge tool.
- Activity timeline + scoring — each logged activity raises a contact's score via a listener; a scheduled command decays stale scores so the ranking reflects recent engagement, not all-time noise.
The package-worthy bit is the scoring flow: event (ActivityLogged) → listener (AwardScoreForActivity) → a service applying rule-based points, with a scheduled decay command. Side effects stay out of the controller.
Also landed a small "MCP Tokens" settings page across apps — mint/revoke personal access tokens for MCP access.
What's next
A Pest pass on the wizard's column-mapping edge cases (duplicate keys, empty columns), and a driver-based abstraction for the scoring rules so point values aren't hard-coded. Tomorrow's problem.