Updated each Sunday at 9 AM — up to 25 of the highest-scored upcoming shows on avlgo.com are selected (its event score weighs how rare, novel, and large-scale each event is), listed by date, and the top Spotify track for each headliner is added to the playlist.
| Date | Artist | Venue | Spotify pick | Tickets |
|---|
A Laravel Artisan command built for the Curitics Care-Management app to stress-test it at production scale and beyond. Generates N new patient records plus proportional related data (medication refills, conditions, care gaps, notes, tasks, plans) so performance benchmarks exercise the queries that actually get slow in prod.
Command lives at: app/Console/Commands/Performance/VolumeSeedCommand.php
Production had ~500K patients when this work started. The goal was to find out what happens at 1M, 3M, and beyond — before prod got there.
The previous version of this gist claimed php artisan optimize should be moved from build to deploy because cached views/routes contain wrong file paths. That's incorrect. Cached Blade views only contain path references in PHP comments (/**PATH ... ENDPATH**/), not in executable code. Laravel resolves paths dynamically at runtime.
Moving optimize to deploy actually breaks the deploy because Lambda's /var/task is read-only and event:cache/view:cache can't write there.
The standard Vapor template (optimize in build) is correct. Don't change it.
Both solve the same problem: your feature branch is behind upstream and you want the latest code.
PR: https://github.com/curiticshealth/Care-Management/pull/2929 Merged: 2026-03-25
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.
| 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.
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
Filament ships two separate layers that must stay in sync:
composer update)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.
General uptime monitoring + catching intermittent TLS failures on specific AWS API Gateway nodes.
Domains: cm.curiticspulse.com (production) · cm-uat.curiticspulse.com (UAT)
Date: 2026-03-19
cm-uat.curiticspulse.com and a client on cm.curiticspulse.com both seeing ERR_SSL_PROTOCOL_ERROR in Chrome on Windows