Conversation
ph.archcore.ai is on the list of subdomain prefixes PostHog itself names as targeted by content blockers, alongside analytics, tracking and telemetry. It also spent months dead — its Vercel deployment went away with the landing site's move to GitHub Pages, and every beacon from here got a 404 nobody saw. Both are fixed by moving to a neutral name behind a PostHog managed reverse proxy. defaultEndpoint has no environment override, so a released binary reports to whatever host it was built with, forever. ph.archcore.ai therefore stays alive as a second proxy on the same project until builds carrying this change have propagated; the comment records why, so the next person does not delete it. Not shipped until the CNAMEs answer — see the cutover checklist in analytics-host-must-reach-posthog.adr.md in archcore-ai/landing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TJ1vhqTmechbRGqMmhuBEH
Three .archcore documents still named ph.archcore.ai as the ingestion host. The beacon ADR also listed "resolves to Vercel, unreliable in Russia" as a hypothetical drawback — that risk had already fired: the deployment behind that host was deleted with the landing site's move to GitHub Pages and every beacon got a 404 for months. Recorded as what happened, with the CI check that now prevents it, rather than as a risk still ahead of us. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TJ1vhqTmechbRGqMmhuBEH
Contributor
Author
|
Схлопнуто в e33df77 напрямую в main. Diff ветки к main пустой — закрываю как дубль. |
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.
Why
ph.archcore.ai— the hostinstall.sh,install.ps1and the CLI binary all report to — spent months returning404 DEPLOYMENT_NOT_FOUND. Its Vercel deployment went away with the landing site's move to GitHub Pages, and nothing failed: every beacon got a 404 nobody read.It is also a name PostHog itself flags. Its guidance lists
phalongsideanalytics,tracking,telemetryandposthogas subdomain prefixes content blockers target — on the one host whose entire purpose is to stay unblocked.Both are fixed by
edge.archcore.ai, a PostHog managed reverse proxy that is now live and verified end to end (POST /i/v0/e/→200 {"status":"Ok"}from a real browser).What changes
install.sh:30andinstall.ps1:20→https://edge.archcore.ai.internal/telemetry/telemetry.godefaultEndpoint→https://edge.archcore.ai/i/v0/e/, plus a comment recording why the old host cannot simply be deleted.internal/telemetry/telemetry_test.go.go build ./...andgo test ./internal/telemetry/pass.Why ph.archcore.ai stays alive
defaultEndpointhas no environment override, so a released binary reports to whatever host it was built with, for the rest of its life.ph.archcore.aiis therefore kept as a second managed proxy on the same PostHog project until builds carrying this change have propagated. Deleting it now would silence every already-installed CLI.After merging
A release is needed for this to reach users. The landing repository re-syncs
install.shandinstall.ps1on its next deploy, and only then can the installer host check there be flipped fromMODE: warnto a hard gate.Full context and the cutover checklist:
analytics-host-must-reach-posthog.adr.mdinarchcore-ai/landing.🤖 Generated with Claude Code
https://claude.ai/code/session_01TJ1vhqTmechbRGqMmhuBEH