Repository navigation
feat: serve Reports from an engine service over packs - #44
Merged
Merged
Conversation
…k, lockfile and generated changes
…, Sentry traces and PostHog events
…d remove the crowd features
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
…elying on test order
One config file, apps/site/src/lib/analytics-config.ts, lists every kind of usage data and, per region of countries, what runs before the visitor chooses, at Only basic and at Allow all. The EU, the EEA, the UK, Switzerland and India start at basic; everywhere else starts at all. - The browser runs PostHog cookieless until the visitor allows all, then adds autocapture, rage and dead clicks, heatmaps, session replay with console, network timings and canvas, and identifies the person. - A banner in the corner, Settings and the privacy page set the choice. - /ingest forwards the part of the address the level allows, for GeoIP. - The server's events follow the same level and join the browser's session; Cards, Shared Reports and App installs are counted too. - Delete my data also deletes the person in PostHog. - The privacy page is drawn from the config.
share, health, surviving and report each send one count to the Site's /api/telemetry: the command, how long it took, how it ended, the version and the platform, under a random install id kept in the cache folder. The first run says so; COMMITSCAPE_TELEMETRY=0 or DO_NOT_TRACK=1 turns it off. The Site checks every field, limits each address, and passes it to PostHog at the region's level. Tests run the binary with it off.
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.
Rebuilds how a repository's Report is built and served.
What changes
commitscape buildwrites the Postgres export, the pack and the Report's meta from one reading of the history.apps/engine, new): Rust (axum, tokio) answering every question the Site used to work out in Node, from immutable packs in R2, kept on disk and in memory. Bearer token, golden tests against the old answers, its own Docker image.rebuildcommand; Sentry traces continue from the Site's request, PostHog events under a hashed id./mcpstay public), Leaderboards, Races, Crews, Seasons and Rivals removed, Sentry no longer sends cookies, headers or IPs, requests named by route, PostHog through/ingest.apps/landing, new): static, for Cloudflare Pages.app.commitscape.com.Measured on react (35k commits)
Checks
cargo fmt, clippy, layering and 291 Rust tests; every package's typecheck, lint, build and tests;pnpm e2e61/61.Deploying
Deploy all three images together on an empty database and bucket, then run
node builder.mjs rebuildif anything was built before the engine service existed.DEPLOY.mdhas every setting.