Rowan

Ask locally before you order plants. Cuttings of pothos, ficus pumila and tradescantia are what keepers throw away every time they trim a tank, and I have never paid for any of the three.

You ran it locally. Without --remote that command hits the miniflare SQLite file under .wrangler/state/v3/d1/, not your actual database. Exit code 0 because it genuinely succeeded - just not where you thought.

For tonight:

wrangler d1 execute app-db --remote --file=./migrations/0004_sessions.sql

For good:

wrangler d1 migrations apply app-db --remote

The second one tracks what has been applied in a d1_migrations table, so it is safe to run repeatedly and it will not reapply 0001 through 0003.

And yes, wrangler dev is local-first by default too, which is exactly why your dev environment agreed with you the whole time.

Chunks of 100 took a 2,400 row import from timing out to 1.9 seconds. I had read "subrequest" as meaning outbound fetch only and never connected it to database calls.

That waitUntil detail would have cost me a day, it was going to be my next attempt.

The no-down-migration thing feels primitive right up until you admit you have never once successfully run a down migration against a production database in your life. I certainly have not, and I wrote hundreds of them.

Disagreeing with the framing rather than the maths. A garden window is a house decision, not a herb decision. If you want one because you like the look and you are keeping the house for a decade, get one and enjoy the herbs as a bonus. If you are justifying it with basil, you will resent it the first time you see a water stain on the plaster under the sill.

hourly CUR into athena, alert on deviation from the trailing median, page the on-call rotation. quotas so the worst case is bounded while you sleep.

Very cheap thing that helped on the worst nights: a damp flannel in the freezer for ten minutes, on the back of the neck. Not a solution, but it got me through a heatwave when nothing else did.

Worth knowing CORS rule changes take a minute or two to propagate, so do not conclude your fix failed after one immediate retry. I have reverted two correct fixes that way.

If you must add one, add the one that makes the others cheaper. That is the bedtime, every time.

Worth adding that a physio who works with musicians is a different creature from a general one. The first general physio I saw told me to rest for six weeks, which does nothing about the technique that caused it and costs you six weeks.

Three seasons on an inflatable will do that. Also check inflation pressure, an underinflated pad lets your hip bottom out and you get a direct conduction path.

Temperature ratings are frequently limit or survival ratings rather than comfort ratings, and they are measured on a manikin wearing a full base layer set and a hood. A 30F quilt being a comfortable 40F quilt for a cold sleeper is not a defect, it is the normal offset. I plan on 10-15F of margin as standard and have never regretted it.

Thick leaves live, thin leaves die, and your gecko will flatten anything under 15cm tall. Plant high, plant tough.

Morning light did it for me. Fifteen minutes outside within half an hour of waking, every day including weekends. Took about ten days to notice anything. It does not stop the waking directly, it seems to make the whole night sit in a more consistent place.

Everyone goes through it and it is oddly under-discussed. Three or four days is the standard adaptation window, your body is adjusting to carrying load all day, to eating differently, and usually to sleeping badly on the first night or two, all at once.

Things that shorten it: eat much more on days one and two than you think you need, start slower than feels natural on day one, and make the first day the shortest of the trip rather than the biggest. Most people do the opposite because they are fresh and excited, then pay for it for three days.

Did not know these were public. Found four logs within half a mile of the lot in about ten minutes.

That explains the per-foot one with no total. It is drilling only and I was reading it as the whole job.

Slightly different read: with one large animal producing large waste, the cleanup crew is probably undersized rather than dead. A snake tank needs a much heavier isopod population than a gecko tank of the same size, and if you seeded once at setup you have not kept up with the load.

Second the per-room design, and be careful where you put the index. A single DO holding "which rooms exist" recreates the bottleneck you were trying to avoid, just at a lower request rate: until you add presence and it gets written on every join and leave.

D1 for room metadata, KV for things read constantly and written rarely, DO storage for live document state. Three stores sounds like a lot until you notice each one is doing the thing it is good at.

This is why my local place lost my nicer knives. Came back sharp, came back with a visibly different heel, and the tip was a slightly different shape.

Drop the liner sock and try one well-fitted sock. The two-sock system is meant to move friction between the layers, but with a half size up and two socks a lot of people end up with the whole stack sliding inside the shoe instead, and the heel is where that shows first.

Then lock your heel down with the lacing. Use the top eyelet as a heel lock, thread the lace back into the same side's top eyelet to make a loop, cross through the opposite loop, pull snug. Ten seconds, and it is the single biggest change for heel blisters I have made.

Day one fine and day two blistered is also a swelling story. Your feet are bigger on day two. Loosen the forefoot and keep the heel lock tight.

It does not, honestly. I picked 6:30 because it sounded like what a disciplined person does.

I am definitely on a bright laptop until I close it and get into bed. That is an obvious hole in what I was doing.

It comes down to where your reads have to travel, and both options have a version of that problem.

D1: 2 GB is well inside the limit, and 30 req/s of indexed reads is not a challenging number. The catch is that writes go to a primary, so a user far from it pays the round trip on anything that writes, and read replication is what you reach for to keep reads local. With 1% writes that trade looks good for you.

Neon from a Worker: use the serverless HTTP driver, not a TCP pool. There is no connection to keep warm over HTTP, which is the only reason this is viable from an isolate at all. What you are paying instead is a full round trip to whatever region your Neon project lives in, on every query. If the Worker runs in Sydney and Neon is in Virginia, that is 200ms+ before the query even starts, and your three-join dashboard page issuing four queries in sequence is now a second of pure network.

Decision rule I would use: if you want Postgres features you can name - real window functions, extensions, pgvector later: take Neon and stop pretending the Worker's location matters, put your logic where the data is. If your queries are boring and latency is the product, take D1.