Files
zeekay 1b367e2b62 chore: rebase the tree onto upstream master
The tree was a debranded snapshot of upstream taken around 2026-02-20, and
upstream has moved about five months since. This replaces it with upstream
master, mechanically re-derived: bin/debrand does the rename, and the
pipeline and squashed migrations are restored from the shipped tree.

Not a merge. The previous import replaced the tree wholesale in a single
commit, so there is no shared content history to merge against. Reproducing
the rename on the new tree is what actually converges.

What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints,
compose files, LLM.md, and insights/migrations. The squashed initial
migration is load-bearing — the live database records it by name, so
upstream's ~918 individual migrations cannot come back.

Nine products are dropped as unreferenced. Twenty-one more that we do not run
are kept anyway because the core app still imports them; unpicking those is a
refactor and does not belong in a rebase.

This base does not build yet, and the reasons are not in the rename:
upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against
our 4.2, and the dependency manifests still name upstream packages that we
republish under our own names. Those are decisions, not renames.
2026-08-01 15:44:40 -07:00

74 lines
2.7 KiB
TypeScript

import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
import { StepDefinition } from '../steps'
export const getRudderstackSteps = (ctx: OnboardingComponentsContext): StepDefinition[] => {
const { CodeBlock, Markdown, CalloutBox, dedent } = ctx
return [
{
title: 'Add Insights destination',
badge: 'required',
content: (
<Markdown>
RudderStack is an open-source customer data platform that can route your analytics data to Insights
and other destinations. In your RudderStack dashboard, go to **Destinations** &gt; **Add
Destination** and search for **Insights**.
</Markdown>
),
},
{
title: 'Enter your credentials',
badge: 'required',
content: (
<>
<Markdown>Enter your Insights project token:</Markdown>
<CodeBlock
blocks={[
{
language: 'text',
file: 'API Key',
code: dedent`
<ph_project_token>
`,
},
]}
/>
<Markdown>Enter your Insights host:</Markdown>
<CodeBlock
blocks={[
{
language: 'text',
file: 'Host',
code: dedent`
<ph_client_api_host>
`,
},
]}
/>
</>
),
},
{
title: 'Verify the connection',
badge: 'recommended',
content: (
<>
<Markdown>
Connect your source to the Insights destination. RudderStack will now forward `track`,
`identify`, `page`, and `group` calls to Insights.
</Markdown>
<CalloutBox type="fyi" title="Learn more">
<Markdown>
See the [RudderStack integration docs](https://hanzo.ai/docs/libraries/rudderstack) for
more details.
</Markdown>
</CalloutBox>
</>
),
},
]
}
export const RudderstackInstallation = createInstallation(getRudderstackSteps)