Skip to content

Instantly share code, notes, and snippets.

View futzlarson's full-sized avatar

Ryan DuVal futzlarson

3 followers · 1 following
View GitHub Profile
@futzlarson
futzlarson / vapor-env-approaches.md
Last active March 6, 2026 14:56
Approaches to Environment Variables Beyond Vapor's 2KB Lambda Limit

Replacing Vapor's Encrypted Env Files: Approaches & Laravel Integration

Due to AWS Lambda limitations, Vapor environment variables are capped at ~2,000 characters. Vapor's built-in solution — encrypted environment files — works but has significant DX tradeoffs. This document evaluates alternatives with specific attention to how they integrate with Laravel's .env → config() pipeline.

How .env Works in Laravel (and Why It Matters)

Understanding the boot sequence is critical to evaluating alternatives:

@futzlarson
futzlarson / claude-pr-review.md
Last active March 13, 2026 20:01
Claude PR Review: GitHub App vs GitHub Actions vs Local Skill (Laravel Boost)

Claude PR Review: GitHub App vs GitHub Actions vs Local (Laravel Boost)

Option 1 — GitHub App (github.com/apps/claude)

Installed once at the org level via claude.ai/admin-settings/claude-code. Reviews are posted as inline PR comments.

Triggers

  • Auto on PR open/push (configurable)
@futzlarson
futzlarson / gist:7c95c7a7e451fab7769f3ec8d1d46964
Last active March 15, 2026 15:32
Risk Adjustment - Lambda Timeout Analysis Report (2026-03-15)

Risk Adjustment — Lambda Timeout Analysis Report

Date: March 15, 2026
Triggered by: CloudWatch Alarm vapor-Curitics-RA-production-d-timeout-warning
Alarm threshold: 28,000ms (approaching 30s Lambda limit)
Datapoint that fired: 28,877ms at 14:53 UTC

TL;DR

@futzlarson
futzlarson / ssl-investigation.md
Created March 19, 2026 13:39
SSL ERR_SSL_PROTOCOL_ERROR Investigation - curiticspulse.com

SSL Investigation: ERR_SSL_PROTOCOL_ERROR

Domains: cm.curiticspulse.com (production) · cm-uat.curiticspulse.com (UAT) Date: 2026-03-19

What Was Reported

  • An employee on cm-uat.curiticspulse.com and a client on cm.curiticspulse.com both seeing ERR_SSL_PROTOCOL_ERROR in Chrome on Windows
  • Works fine for the developer (macOS)

What Was Checked

@futzlarson
futzlarson / checkly-vs-better-stack.md
Last active March 23, 2026 20:24
Checkly vs Better Stack - Feature & Cost Comparison

Checkly vs Better Stack vs Sentry vs Uptime Kuma vs UptimeRobot

General uptime monitoring + catching intermittent TLS failures on specific AWS API Gateway nodes.

Verdict

  • General monitoring: Start with Checkly Free (6 locations, 1-2 min checks) + Sentry uptime ($1/monitor/month) if you're already on Sentry. Or self-host Uptime Kuma for free on a $5/mo VPS. UptimeRobot Free (50 monitors, 5-min checks) is another solid zero-cost option if you just need simple HTTP pings.
  • Catching today's issue: Checkly Team ($64/mo) — 30s checks across 24 locations with TLS error detail. Better Stack, Sentry, Uptime Kuma, and UptimeRobot all fall short here — single-location or multi-failure requirements mean a bad node in a round-robin pool likely goes undetected.

Comparison

@futzlarson
futzlarson / filament-assets-vapor-gap.md
Last active March 26, 2026 23:48
Care Management: Missing php artisan filament:assets in Vapor build

Missing php artisan filament:assets in Vapor Build

The Problem

Filament ships two separate layers that must stay in sync:

  • PHP — blade templates, component classes, action definitions (updated via composer update)
  • JS — compiled Alpine components published to public/js/filament/ (updated via php artisan filament:assets)

The Vapor build steps run composer install (which pulls the latest PHP), but never run php artisan filament:assets. This means every Filament version bump via composer silently leaves the published JS behind.

@futzlarson
futzlarson / caching.md
Last active April 6, 2026 18:49
Caching

Master Data Caching Strategy (M1–M6)

The application has 140 master_* tables containing reference data (statuses, types, priorities, etc.). These are queried millions of times but rarely change — some are truly static (genders, states, countries), others are modified every few weeks (task statuses, case statuses).

Approach: Cache::flexible() (Laravel 11's stale-while-revalidate) at the model level via a shared trait.

 // Trait added to all Master* models
@futzlarson
futzlarson / cache-invalidation-note.md
Last active April 8, 2026 16:53
Cache invalidation note: rememberForever on master data

Cache Invalidation Note: rememberForever on Master Data

What's cached

Cache Key pattern Used by
CachesIdByName::idByName() App\Models\{Model}:{tenant}:{name} 7 models: MasterTaskStatus, MasterNoteDocStatus, MasterTaskPriority, MasterAssessmentStatus, MasterCaseStatus, MasterCareGapStatus, MasterFileCategory
MasterSmartText::cachedDescriptions() master_smart_texts:{tenant} 20 files — every note, task, assessment, care plan, calendar, and referral form

Both use Cache::rememberForever() with automatic invalidation via Eloquent saved/deleted events.

@futzlarson
futzlarson / autosave-review.md
Created April 8, 2026 17:29
Assessment autosave review (PR #2929) — performance concerns

Assessment Autosave Review (PR #2929)

PR: https://github.com/curiticshealth/Care-Management/pull/2929 Merged: 2026-03-25

Context

The assessment component is the highest-volume transaction in the app — 1.8M Livewire interactions in 2 days (Sentry data). PR #2929 added server-side autosave that fires afterStateUpdated on every form field.

Concerns

@futzlarson
futzlarson / rebase-vs-merge.md
Created April 10, 2026 15:13
Rebase vs Merge: when to use each

Rebase vs Merge: When to Use Each

What they do

Both solve the same problem: your feature branch is behind upstream and you want the latest code.

  • Rebase replays your commits on top of the latest upstream. No extra commits. Clean history.
  • Merge combines the two branches and creates a merge commit as a bookmark.

The only practical difference