PostHog latest self-hosted-viable (cluster remaps + fresh-CH schema-compat) #7
No reviewers
windows
linux
web
runner
agent
billing
manager
infra
cmo
security-agent
devex
cdo
forge
release-runner
assistant
ios
android
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
key-store/key.store!7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/posthog-latest-selfhosted"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Latest PostHog assumes Cloud infra (ai_events/ops ClickHouse clusters, warpstream Kafka named collections). Remap the new cluster settings onto posthog_single_shard and create the CH database before schema-compat. Full migrate now completes (308 CH tables). 🤖 Generated with Claude Code
The latest PostHog image assumes PostHog-Cloud infra its migrations require: - Dedicated ClickHouse clusters (CLICKHOUSE_AI_EVENTS_CLUSTER default 'ai_events', CLICKHOUSE_OPS_CLUSTER default 'ops') that a single-node self-hosted deployment does not define, so ON CLUSTER migrations failed with 'cluster not found'. Remap both onto the existing posthog_single_shard cluster (same pattern the module already uses for CLICKHOUSE_AUX_CLUSTER). - posthog-clickhouse-schema-compat queried the posthog ClickHouse database before migrations create it on a fresh install ('Database posthog does not exist'). Create it over the HTTP interface first (idempotent for existing installs). With these plus the Kafka named collections (msk_cluster + warpstream_*), a full migrate of the latest image completes on the single node (308 CH tables). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>