mirror of https://github.com/hanzoai/insights-go.git synced 2026-09-30 22:46:12 +00:00

Files

T

History

zeekay 0ecfc65ce4 style: gofmt the four files the format gate was never reaching

Import order only, one line per file. These sat unformatted because fmt.yml
filtered on pushes to `main` while this repo's default branch is `master`, so
the check had nothing to look at on the branch every commit lands on. With the
filter corrected the gate ran and named them immediately.

2026-08-13 21:27:44 -07:00

.env.example

feat(flags): Add ETag support for local evaluation polling (#139 )

2025-12-04 11:00:30 -08:00

capture.go

merge: upstream/main (preserve Hanzo brand, 55 commits)

2026-06-02 09:56:19 -07:00

error_tracking.go

fix(build): unify package name to insights (rename stray package posthog); fix leftover posthog. qualifiers in examples + sdk_compliance_adapter

2026-06-30 16:05:00 -07:00

etag_polling.go

rebrand: export Insights types instead of PostHog

2026-03-13 19:54:58 -07:00

featureflags.go

rebrand: export Insights types instead of PostHog

2026-03-13 19:54:58 -07:00

main.go

style: gofmt the four files the format gate was never reaching

2026-08-13 21:27:44 -07:00

README.md

fix: Change default endpoint to us.i.posthog.com (#188 )

2026-04-21 16:11:01 +02:00

README.md

PostHog Go Examples

The examples demonstrate different features of the PostHog Go client.

Running the examples

Option 1: Using .env file (Recommended)

# Copy the example .env file and fill in your credentials
cp .env.example .env
# Edit .env with your actual API keys

# Run all examples
go run *.go

Option 2: Using environment variables

# Set your PostHog API keys
export POSTHOG_PROJECT_API_KEY="your-project-api-key"
export POSTHOG_PERSONAL_API_KEY="your-personal-api-key"

# Run all examples
go run *.go

This will run:

Feature flags example
Capture events example
Capture events with feature flag options example

Prerequisites

Before running the examples, you'll need to:

PostHog API Keys:
- POSTHOG_PROJECT_API_KEY: Your project API key (starts with phc_...)
- POSTHOG_PERSONAL_API_KEY: Your personal API key (starts with phx_...)
PostHog Instance (optional):
- Default: http://localhost:8000
- Set POSTHOG_ENDPOINT in your .env file or environment variables to use a different instance
Feature Flags (for the examples to work properly): Set up the following feature flags in your PostHog instance:
- multivariate-test (a multivariate flag)
- simple-test (a simple boolean flag)
- multivariate-simple-test (a multivariate flag)
- my_secret_flag_value (a remote config flag with string payload)
- my_secret_flag_json_object_value (a remote config flag with JSON object payload)
- my_secret_flag_json_array_value (a remote config flag with JSON array payload)

Configuration

The examples will automatically load configuration from a .env file if it exists using the godotenv library. This provides a convenient way to manage your PostHog credentials without exposing them in your shell history or environment.

.env file format

# PostHog API Configuration
POSTHOG_PROJECT_API_KEY=phc_your_project_api_key_here
POSTHOG_PERSONAL_API_KEY=phx_your_personal_api_key_here
POSTHOG_ENDPOINT=https://us.i.posthog.com

Note: Environment variables take precedence over .env file values, so you can override specific settings when needed.