Repository navigation
Make Unlayer rendering work on a local verification stack #269
Description
Part of #268
Question
Can a local stack render Unlayer designs to html, so the AI-first flow can be verified end to end?
Neither devbox-michaelr-2 nor devbox-michaelr-3 has UNLAYER_API_KEY. It is not in .env and not in the running server's environment. The key lives in 1Password (see .env.local.example), and the devboxes have no op CLI.
Checklist for Michael
- Add
UNLAYER_API_KEY=<key>to~/dev/posthog/.envon the devbox that runs the verification stack. - Restart that stack's web process.
- Comment here with the devbox name.
Resolved when a design-only email patch through workflows-patch-action-email returns rendered html on that stack.
Activity
Silthus commentedon Oct 5, 2026
Decisions locked
UNLAYER_API_KEYset. devbox-michaelr-2 and devbox-michaelr-3 have none, and the devboxes have noopCLI, so the agent cannot fetch it.Pending question for Michael
Which devbox should run the verification stack, once you have added
UNLAYER_API_KEYto its~/dev/posthog/.envand restarted its web process?Silthus commentedon Oct 5, 2026
Blocked, closed (Michael, 2026-10-05): no access to the 1Password vault that holds the key. The repo documents the key as
op://General/rf2j5i5qotdt5db37mhswn5dyq/credential(see.env.local.example), resolved bybin/startthrough theopCLI. No local stack can render Unlayer designs until someone with vault access provides it. The live proof on AI-first draft creates emails as native blocks with readable spacing stays pending for Michael.