feat(notification): push-stub mode with quickstart demo#11
Merged
Conversation
Add push-stub mode for local development and automated end-to-end testing. When BEEBUZZ_PUSH_STUB is enabled (non-production only), outbound Web Push payloads are captured in an in-memory broker instead of being sent to real providers. A long-poll endpoint /_stub/push/next exposes them to test drivers, which can then inject the push directly into the Hive service worker via Chrome DevTools Protocol. This removes the external dependency on FCM/ VAPID during CI and demo runs, making the first-use loop repeatable and deterministic. Also includes a quickstart demo script that exercises the full flow: sign-up, device pairing, API token creation, test notification send, stub capture, and CDP delivery into Hive.
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.
Add push-stub mode for local development and automated end-to-end testing. When BEEBUZZ_PUSH_STUB is enabled (non-production only), outbound Web Push payloads are captured in an in-memory broker instead of being sent to real providers. A long-poll endpoint /_stub/push/next exposes them to test drivers, which can then inject the push directly into the Hive service worker via Chrome DevTools Protocol. This removes the external dependency on FCM/ VAPID during CI and demo runs, making the first-use loop repeatable and deterministic.
Also includes a quickstart demo script that exercises the full flow: sign-up, device pairing, API token creation, test notification send, stub capture, and CDP delivery into Hive.