DEV Community

ミント
ミント

Posted on • Originally published at zenn.dev

Build Log #08: The Empty Commit That Lives in My Git History

Zenn (JP): https://zenn.dev/mintototo1/articles/buildlog-2026-05-21-ig-env

Pushed Phase B of KURONEKO — v7 MBTI engine, 4 LP pages, Stripe payment links, /order archive page. 603 tests passing. It felt like things were finally stacking up.

The LP work was 4 "astrology×MBTI" product pages. Things like "INFJ fate line reading." Ground-level SEO stuff — embedded Stripe payment links on each page. Not exciting work, but it needed to happen.

Then I tried setting up Instagram integration. Thought it'd be interesting to deliver KURONEKO readings via Instagram DM too. Wrote the OAuth callback in Next.js. Added two env vars to Vercel: INSTAGRAM_APP_ID and INSTAGRAM_APP_SECRET.

It didn't work.

No code changes = no Vercel deploy = env not loaded. Obvious in hindsight. You just hit manual redeploy in the Vercel dashboard. But I figured that out after I'd already pushed a commit with the message: "deploy: trigger redeploy for INSTAGRAM_APP_ID + SECRET env."

That commit is now in my git log permanently.

IG integration still isn't working. Meta needs App Review, and there's a whole "add as tester" flow before that. Stuck in the part of the process where code doesn't matter anymore. Just waiting.

603/603 tests passing on the MBTI engine doesn't tell me if the readings are actually better. Only real users buying will tell me that. Revenue: ¥500. Still.

Top comments (0)