Prepare free BorderPulse app for a cost-controlled Vercel preview - #103
Merged
Merged
Conversation
This was referenced Sep 30, 2026
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
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.
Purpose
Prepare the current free, ad-supported BorderPulse app for a Vercel preview without switching the public domain or introducing Supabase, Sentry, auth, or billing.
Changes
Cost boundary
Do not connect each 15-minute data commit to a Vercel frontend build. The live function fetches data independently; the history artifact is refreshed by the existing GitHub writer. A production move still needs a preview readback, usage/spend review, an update plan for historical aggregates, and Sebastian's explicit approval.
Review evidence
git diff --cached --checkpassed before commit; snapshot writer produced 388 compact observations (820 KB) from the current 30-day history.Tracks #101.