feat(www): proxy Plausible through usewraith.xyz, document dashboard access - #119
Open
Noubata wants to merge 1 commit into
Open
feat(www): proxy Plausible through usewraith.xyz, document dashboard access#119Noubata wants to merge 1 commit into
Noubata wants to merge 1 commit into
Conversation
…access Closes wraith-protocol#79. Serves the analytics script and event beacon from our own domain via vercel.json rewrites instead of plausible.io directly, so no analytics request is cross-origin. Also documents that the Plausible dashboard is internal-only rather than public.
|
@Noubata is attempting to deploy a commit to the truthixify's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@Noubata Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Summary
Closes #79.
Most of the cookie-less analytics work landed already in #47 (Plausible script,
trackEvent()helper, Privacy page copy). This PR closes the remaining gaps against the ticket's acceptance criteria:plausible.io.vercel.jsonnow proxies/js/script.jsand/api/eventto Plausible's servers server-side, andindex.htmlloads the script from/js/script.js(same-origin). Plausible derives its event endpoint from the script's own origin, so events also post tousewraith.xyz/api/eventautomatically.docs/CONTRIBUTING.md(team-invite access) and noted briefly insrc/pages/Privacy.tsx.docs/CONTRIBUTING.mdandsrc/pages/Privacy.tsxcopy to reflect the proxy setup.Note: this proxies Plausible's cloud service through our domain rather than self-hosting the Plausible app (Postgres/ClickHouse) itself — self-hosting would need real infra provisioning, out of scope for an S-tier ticket. The proxy achieves the same practical outcome (no cookies, no cross-origin requests, ad-blocker resilient).
Test plan
pnpm install && pnpm format:check && pnpm build(not run in this environment — no Node available)pnpm dev, load every route, confirm in DevTools Network tab: script loads fromusewraith.xyz/js/script.js, event beacons post tousewraith.xyz/api/event, zero requests toplausible.io