mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekay
1b367e2b62
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.
59 lines
2.5 KiB
TypeScript
59 lines
2.5 KiB
TypeScript
import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
|
|
|
|
import { StepDefinition } from '../steps'
|
|
|
|
export const getHeliconeSteps = (ctx: OnboardingComponentsContext): StepDefinition[] => {
|
|
const { CodeBlock, Markdown, dedent } = ctx
|
|
|
|
return [
|
|
{
|
|
title: 'Set up Helicone',
|
|
badge: 'required',
|
|
content: (
|
|
<Markdown>
|
|
Helicone supports most popular LLM models and you can bring your Helicone data into Insights for
|
|
analysis. Sign up to [Helicone](https://www.helicone.ai/) and add it to your LLM app.
|
|
</Markdown>
|
|
),
|
|
},
|
|
{
|
|
title: 'Add Insights headers',
|
|
badge: 'required',
|
|
content: (
|
|
<>
|
|
<Markdown>
|
|
Similar to how you add a [Helicone-Auth
|
|
header](https://docs.helicone.ai/helicone-headers/header-directory#supported-headers) when
|
|
installing Helicone, add two new headers **Helicone-Insights-Key** and **Helicone-Insights-Host**
|
|
with your Insights details:
|
|
</Markdown>
|
|
<CodeBlock
|
|
blocks={[
|
|
{
|
|
language: 'python',
|
|
file: 'Python',
|
|
code: dedent`
|
|
# Example for adding it to OpenAI in Python
|
|
|
|
client = OpenAI(
|
|
api_key="your-api-key-here", # Replace with your OpenAI API key
|
|
base_url="https://oai.hconeai.com/v1", # Set the API endpoint
|
|
default_headers={
|
|
"Helicone-Auth": f"Bearer {HELICONE_API_KEY}",
|
|
"Helicone-Insights-Key": "<ph_project_token>",
|
|
"Helicone-Insights-Host": "<ph_client_api_host>",
|
|
}
|
|
)
|
|
`,
|
|
},
|
|
]}
|
|
/>
|
|
<Markdown>Helicone events will now be exported into Insights as soon as they're available.</Markdown>
|
|
</>
|
|
),
|
|
},
|
|
]
|
|
}
|
|
|
|
export const HeliconeInstallation = createInstallation(getHeliconeSteps)
|