Build Log: Day 4 — Deploying the Thing I'd Already Built

Day 4's task sounded like a formality: the automation already ran fine on my machine, so I figured pushing it live was just one command and a checkmark.

What I deployed was the daily newsletter digest I'd built earlier in the challenge — a scheduled job that pulls fresh articles from nine RSS feeds every morning and hands them to Claude to turn into one short digest, no manual pulling required.

The deploy command didn't agree with my plan. It threw an error about a missing file, except the file was right there. The real issue was almost funny: my project folder is named "trigger demo," with a space in it, and the system pushing code to the cloud choked on that space and went looking for a file path that, as far as it was concerned, didn't exist.

I tried a quick patch first — a second, no-space folder name pointing back at the original. Didn't work; the deploy tool saw through it and landed on the same error. What actually fixed it was switching to a different way of pushing code entirely, one that doesn't care whether the folder paths match between my machine and the cloud. Deploy went through clean on the first try after that, and I locked the setting in so I never have to think about it again.

The lesson: a workaround that just routes around the symptom can lead you right back to the same wall. The real fix was picking a different road, not patching the broken one.

Next up, I want to watch this thing fire on its own schedule for a few mornings without me checking on it.

Anyone else had a deploy choke on something this small?

(Images below: the deploy-fix diagram first, then the completed run in the Trigger.dev dashboard.)

3 comments

Build Log: Day 4 — Deploying the Thing I'd Already Built