What comes in Writing Markdown in the code editor a commit is the publish button Markdown · git
Storyus stories, albums, panoramas webhook
Photographs Cloudinary · Flickr API
The house Sigenergy · Octopus Energy NESO · SSEN API
The lamp a Shelly plug on my desk API
Bluesky profile, feed and records AT Protocol
↓ Writing goes to the content library; the feeds are read by the scheduler.
The application The content library What is published, and where posts, pages, Storyus pieces, experiments 41 legacy redirects, feeds and the sitemap drafts only after signing in Collections · Cache · Routing
The scheduler Work while nobody is looking the house every 30 minutes, today every hour completed days replayed after midnight the carbon comparison, the profile update content health checks, with an email Scheduler · Artisan · Cloud cron
The store The memory the pages read from snapshots, histories, counters, timings a copy to private storage twice a day Valkey · Cache
AI, when you ask for it A model runs only on a press never on a page view or a prefetch AI SDK · Vercel AI Gateway
↓ The store is what the pages and the live house read from.
What visitors get Pages Rendered on the server, then instant readable before any JavaScript arrives the main destinations fetched quietly, so the next click is there no cookies on public pages, so the edge can serve them whole Inertia · React · SSR
The house, live Pushed, not polled solar, battery, grid, the lamp suns from completed days today hatched until confirmed Reverb · Echo · managed
Pictures of the site Share images, on deploy one per post and page, by hash photographs at the right size a speaker kit for hosts Satori · sharp
Measured from real visits Two tiny beacons per page first byte, largest paint, layout shift, in-site clicks histograms by page, device and country; nothing identifies anyone lab runs kept apart from people Routing · Cache · rate limits
Laravel Cloud · what runs it Compute one Flex instance hibernates when idle, wakes for a visitor or a scheduled task Scheduler platform-run cron every minute, waking the app when needed: energy, Storyus, mail Valkey managed cache the store: snapshots, counters, flags, locks, histograms Object storage two buckets public: the travel photographs; private: the daily copies WebSockets managed Reverb the live house, pushed to every open page Edge network CDN · bots · TLS pages and assets kept close by; the domain; purged on publish Push to deploy from main the build warms the caches; zero-downtime switch, then a check Previews one per branch a branch gets its own review environment; gone when it merges Environment variables, secrets credentials injected by Cloud; every key here, none in code
What everything stands on Delivery and freshness Stale, never slow fresh for five minutes, then served while renewed; purged the moment a post or story changes assets versioned, cached for a year Edge · Cloudflare
The private side Behind a sign-in, always drafts, previews, the library's controls the household's own energy review flags decide what an experiment does, never who may see something private Authentication · Pennant
Quality, before a commit Checked before it ships tests, types, Pint and a browser suite pages read with JavaScript off and on a smoke check after every deploy local timings never called production PHPUnit · Playwright · Pint
Watched by Nightwatch Production, seen from inside requests, queries and outgoing calls to the house, Storyus and the rest exceptions and logs, with alerts connected from Cloud in one step Nightwatch