Feat/storefront live preview - #805
Open
HananINouman wants to merge 2 commits into
Open
Conversation
Render session-only branding drafts through the real public storefront so operators can preview safely without duplicating buyer UI. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep operator live previews on storefront-preview.obol.stack (never the public tunnel), retain that renderer when the public catch-all is torn down, and use server-side apply so large inline logos survive kubectl's 256 KiB last-applied annotation limit.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Real storefront preview — The operator dashboard previews the actual buyer storefront rather than maintaining a duplicated implementation.
Local-only preview route —
storefront-preview.obol.stackis created automatically byobol stack upand is never published through Cloudflare.Secure iframe boundary — CSP restricts framing to
obol.stack; the iframe is sandboxed, messages require the expected window/origin, and draft payloads are validated.No automatic publishing — Branding changes remain session-only until the operator explicitly runs the generated
obol sell info setcommand.Payment safety — Payment, wallet, and other interactive controls are disabled in preview mode while scrolling remains available.
Independent lifecycle — Removing the public storefront route or stopping a quick tunnel does not remove the local preview renderer.
Large logo support — Storefront profiles use server-side apply, avoiding Kubernetes’ 262144-byte
last-applied-configurationannotation limit.Correct development image — Dynamic storefront resources use the locally built per-commit image instead of accidentally running stale
:latest.