Dev Log: 2026-06-27

작성자

카테고리:

← 피드로
DEV Community · Nasrul Hazim Bin Mohamad · 2026-06-28 개발(SW)
Cover image for Dev Log: 2026-06-27

Nasrul Hazim

1 Dev Log: 2026-06-19 — MCP Servers Everywhere, Email That Tracks Itself, and Menus That Behave 2 Dev Log: 2026-06-22 — Configurable Schedulers, Load-Test Toolkits, and an MCP Server … 18 more parts… 3 Dev Log: 2026-06-23 — Query Cleanups, Real Health Checks, Safer MCP Tools, and Password-Reset Plumbing 4 Dev Log: 2026-06-24 — agent guardrails and runtime LDAP config 5 Dev Log: 2026-06-25 — Driver Seams Everywhere, a Tracking-URL Bug, and DB-Backed Settings 6 Dev Log: 2026-06-26 — Config-Driven Billing, an App-Wide Rebrand, and Branded Error Pages 7 Dev Log: 2026-06-27 8 Dev Log: 2026-06-28 9 Dev Log: 2026-06-29 10 Dev Log: 2026-06-30 11 Dev Log: 2026-07-01 12 Dev Log: 2026-07-02 — disable means drain, and case never matters 13 Dev Log: 2026-07-03 — idempotent syncs, mail you can trace, and drain-not-delete 14 Dev Log: 2026-07-04 15 Dev Log: 2026-07-05 16 Dev Log: 2026-07-06 17 Dev Log: 2026-07-07 18 Dev Log: 2026-07-09 — one source of truth, three times over 19 Dev Log: 2026-07-14 20 Dev Log: 2026-07-15 21 Dev Log: 2026-07-16 22 Dev Log: 2026-07-19

TL;DR

  • Shipped a composer share command + 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.

1 Dev Log: 2026-06-19 — MCP Servers Everywhere, Email That Tracks Itself, and Menus That Behave 2 Dev Log: 2026-06-22 — Configurable Schedulers, Load-Test Toolkits, and an MCP Server … 18 more parts… 3 Dev Log: 2026-06-23 — Query Cleanups, Real Health Checks, Safer MCP Tools, and Password-Reset Plumbing 4 Dev Log: 2026-06-24 — agent guardrails and runtime LDAP config 5 Dev Log: 2026-06-25 — Driver Seams Everywhere, a Tracking-URL Bug, and DB-Backed Settings 6 Dev Log: 2026-06-26 — Config-Driven Billing, an App-Wide Rebrand, and Branded Error Pages 7 Dev Log: 2026-06-27 8 Dev Log: 2026-06-28 9 Dev Log: 2026-06-29 10 Dev Log: 2026-06-30 11 Dev Log: 2026-07-01 12 Dev Log: 2026-07-02 — disable means drain, and case never matters 13 Dev Log: 2026-07-03 — idempotent syncs, mail you can trace, and drain-not-delete 14 Dev Log: 2026-07-04 15 Dev Log: 2026-07-05 16 Dev Log: 2026-07-06 17 Dev Log: 2026-07-07 18 Dev Log: 2026-07-09 — one source of truth, three times over 19 Dev Log: 2026-07-14 20 Dev Log: 2026-07-15 21 Dev Log: 2026-07-16 22 Dev Log: 2026-07-19

원문에서 계속 ↗

추출 본문 · 출처: dev.to · https://dev.to/nasrulhazim/dev-log-2026-06-27-3ajj

코멘트

답글 남기기

이메일 주소는 공개되지 않습니다. 필수 필드는 *로 표시됩니다