vybekiit 0.7.26 → 0.7.27

package/dist/global-skills/instrument-product-analytics/references/elixir.md

@@ -1,10 +1,6 @@
 > AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
 
-# Elixir - Docs
-
-Copy page
-
-# Elixir - Docs
+# Elixir
 
 This library provides an Elixir HTTP client for PostHog. [See the repository](https://github.com/posthog/posthog-elixir) for more information.
 
@@ -16,8 +12,6 @@ The package can be installed by adding `posthog` to your list of dependencies in
 
 Elixir
 
-PostHog AI
-
 ```elixir
 def deps do
   [
@@ -30,8 +24,6 @@ end
 
 config/config.exs
 
-PostHog AI
-
 ```elixir
 config :posthog,
   enable: true,
@@ -60,8 +52,6 @@ To capture an event, use `PostHog.capture/2`:
 
 Elixir
 
-PostHog AI
-
 ```elixir
 PostHog.capture("user_signed_up", %{distinct_id: "distinct_id_of_the_user"})
 ```
@@ -74,8 +64,6 @@ Optionally, you can include additional information with the event by including a
 
 Elixir
 
-PostHog AI
-
 ```elixir
 PostHog.capture("user_signed_up", %{
   distinct_id: "distinct_id_of_the_user",
@@ -92,8 +80,6 @@ The context is stored in the `Logger` metadata and PostHog automatically attache
 
 Elixir
 
-PostHog AI
-
 ```elixir
 PostHog.set_context(%{distinct_id: "distinct_id_of_the_user"})
 PostHog.capture("page_opened")
@@ -103,8 +89,6 @@ You can also scope the context to a specific event name:
 
 Elixir
 
-PostHog AI
-
 ```elixir
 PostHog.set_event_context("sensitive_event", %{"$process_person_profile": false})
 ```
@@ -125,8 +109,6 @@ For example:
 
 Elixir
 
-PostHog AI
-
 ```elixir
 PostHog.capture("$create_alias", %{distinct_id: "frontend_id", alias: "backend_id"})
 ```
@@ -135,8 +117,6 @@ PostHog.capture("$create_alias", %{distinct_id: "frontend_id", alias: "backend_i
 
 Elixir
 
-PostHog AI
-
 ```elixir
 PostHog.capture("$groupidentify", %{
   distinct_id: "static_string_used_for_all_group_events",
@@ -151,8 +131,6 @@ For Phoenix or Plug apps, add `PostHog.Integrations.Plug` before your router to
 
 lib/my\_app\_web/endpoint.ex
 
-PostHog AI
-
 ```elixir
 plug PostHog.Integrations.Plug
 plug MyAppWeb.Router
@@ -162,14 +140,14 @@ For plain Plug routers, add it before `:match` and `:dispatch`:
 
 Elixir
 
-PostHog AI
-
 ```elixir
 defmodule MyRouter do
   use Plug.Router
+
   plug PostHog.Integrations.Plug
   plug :match
   plug :dispatch
+
   # ... routes
 end
 ```
@@ -194,10 +172,9 @@ Call `PostHog.FeatureFlags.evaluate_flags/1` once for the user, then read values
 
 Elixir
 
-PostHog AI
-
 ```elixir
 {:ok, snapshot} = PostHog.FeatureFlags.evaluate_flags("distinct_id_of_your_user")
+
 if PostHog.FeatureFlags.Evaluations.enabled?(snapshot, "flag-key") do
   # Do something differently for this user
   # Optional: fetch the payload
@@ -209,11 +186,11 @@ end
 
 Elixir
 
-PostHog AI
-
 ```elixir
 {:ok, snapshot} = PostHog.FeatureFlags.evaluate_flags("distinct_id_of_your_user")
+
 enabled_variant = PostHog.FeatureFlags.Evaluations.get_flag(snapshot, "flag-key")
+
 if enabled_variant == "variant-key" do
   # Do something differently for this user
   # Optional: fetch the payload
@@ -239,13 +216,13 @@ Put the same `snapshot` object that you used for branching into context. Subsequ
 
 Elixir
 
-PostHog AI
-
 ```elixir
 {:ok, snapshot} = PostHog.FeatureFlags.evaluate_flags("distinct_id_of_your_user")
+
 if PostHog.FeatureFlags.Evaluations.enabled?(snapshot, "flag-key") do
   # Do something differently for this user
 end
+
 PostHog.FeatureFlags.set_in_context(snapshot)
 PostHog.capture("event_name", %{distinct_id: "distinct_id_of_your_user"})
 ```
@@ -256,15 +233,15 @@ To reduce event property bloat, put a filtered snapshot in context:
 
 Elixir
 
-PostHog AI
-
 ```elixir
 {:ok, snapshot} = PostHog.FeatureFlags.evaluate_flags("distinct_id_of_your_user")
+
 # Attach only flags accessed with enabled?/2 or get_flag/2 before this call
 PostHog.FeatureFlags.Evaluations.enabled?(snapshot, "flag-key")
 PostHog.FeatureFlags.set_in_context(
   PostHog.FeatureFlags.Evaluations.only_accessed(snapshot)
 )
+
 # Or attach only specific flags
 PostHog.FeatureFlags.set_in_context(
   PostHog.FeatureFlags.Evaluations.only(snapshot, ["checkout-flow", "new-dashboard"])
@@ -279,8 +256,6 @@ In the event properties, include `$feature/feature_flag_name: variant_key`:
 
 Elixir
 
-PostHog AI
-
 ```elixir
 PostHog.capture("event_name", %{
   "$feature/feature-flag-key" => "variant-key",
@@ -294,8 +269,6 @@ By default, `evaluate_flags/1` evaluates every flag for the user. If you only ne
 
 Elixir
 
-PostHog AI
-
 ```elixir
 {:ok, snapshot} =
   PostHog.FeatureFlags.evaluate_flags(%{
@@ -310,6 +283,34 @@ Capturing `$feature_flag_called` events enables PostHog to know when a flag was
 
 `PostHog.FeatureFlags.Evaluations.get_flag_payload/2` doesn't send `$feature_flag_called` events.
 
+### Local feature flag evaluation
+
+Local evaluation is available in version 2.15.0 and later. Follow the [server-side local evaluation guide](/docs/feature-flags/local-evaluation.md) to find your secure key and see how to pass the person properties, groups, and group properties that your flag conditions require.
+
+Store the secure key in a server-side environment variable. Don't expose it to client-side applications:
+
+config/runtime.exs
+
+```elixir
+config :posthog,
+  api_host: "https://us.i.posthog.com",
+  api_key: "<ph_project_token>",
+  secret_key: System.fetch_env!("POSTHOG_FEATURE_FLAGS_SECURE_API_KEY")
+```
+
+When `secret_key` is set, the SDK fetches definitions when it starts and polls for updates every 30 seconds. `PostHog.FeatureFlags.evaluate_flags/1` evaluates each flag locally first. If a flag can't be evaluated locally, the SDK makes one `/flags` request to resolve the remaining flags. Set `only_evaluate_locally: true` in the evaluation map to prevent this remote fallback. The SDK then omits unresolved flags from the snapshot.
+
+Use these configuration options to control local evaluation:
+
+| Option | Default | Purpose |
+| --- | --- | --- |
+| `enable_local_evaluation` | `true` | Starts local evaluation when `secret_key` is set. |
+| `feature_flags_poll_interval_ms` | `30_000` | Sets the interval between definition refreshes. |
+| `flag_definition_request_timeout_ms` | `10_000` | Sets the timeout for each definition request. |
+| `flag_definition_cache_provider_timeout_ms` | `5_000` | Sets the timeout for each shared cache provider callback. |
+
+For multiple server instances, you can implement `PostHog.FeatureFlags.FlagDefinitionCacheProvider` and set `flag_definition_cache_provider: {module, state}`. This optional provider shares definitions and coordinates which instance polls PostHog. See [local evaluation in distributed environments](/docs/feature-flags/local-evaluation/distributed-environments?tab=Elixir.md) for the callback contract and configuration.
+
 ## Error tracking
 
 Error tracking is enabled by default. It will automatically captures exceptions thrown by the application.
@@ -320,8 +321,6 @@ You can always disable it by setting `enable_error_tracking` to false:
 
 Elixir
 
-PostHog AI
-
 ```elixir
 config :posthog,
   enable_error_tracking: false
@@ -335,10 +334,9 @@ In certain cases, you might want to run this supervision tree yourself. You can
 
 config.exs
 
-PostHog AI
-
 ```elixir
 config :posthog, enable: false
+
 config :my_app, :posthog,
   api_host: "https://us.i.posthog.com",
   api_key: "<ph_project_token>"
@@ -346,17 +344,19 @@ config :my_app, :posthog,
 
 application.ex
 
-PostHog AI
-
 ```elixir
 defmodule MyApp.Application do
   use Application
+
   def start(_type, _args) do
     posthog_config = Application.fetch_env!(:my_app, :posthog) |> PostHog.Config.validate!()
+
     :logger.add_handler(:posthog, PostHog.Handler, %{config: posthog_config})
+
     children = [
       {PostHog.Supervisor, posthog_config}
     ]
+
     Supervisor.start_link(children, strategy: :one_for_one)
   end
 end
@@ -368,12 +368,11 @@ In even more advanced cases, you might want to interact with more than one PostH
 
 config.exs
 
-PostHog AI
-
 ```elixir
 config :posthog,
   api_host: "https://us.i.posthog.com",
   api_key: "<ph_project_token>"
+
 config :my_app, :another_posthog,
   api_host: "https://us.i.posthog.com",
   api_key: "a_different_project_api_key",
@@ -382,16 +381,17 @@ config :my_app, :another_posthog,
 
 application.ex
 
-PostHog AI
-
 ```elixir
 defmodule MyApp.Application do
   use Application
+
   def start(_type, _args) do
     posthog_config = Application.fetch_env!(:my_app, :another_posthog) |> PostHog.Config.validate!()
+
     children = [
       {PostHog.Supervisor, posthog_config}
     ]
+
     Supervisor.start_link(children, strategy: :one_for_one)
   end
 end
@@ -401,8 +401,6 @@ Then, each function in the PostHog module accepts an optional first argument wit
 
 Elixir
 
-PostHog AI
-
 ```elixir
 PostHog.capture(AnotherPostHog, "user_signed_up", %{distinct_id: "user123"})
 ```

package/dist/global-skills/instrument-product-analytics/references/flask.md

@@ -1,10 +1,6 @@
 > AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
 
-# Flask - Docs
-
-Copy page
-
-# Flask - Docs
+# Flask
 
 PostHog makes it easy to get data about traffic and usage of your Flask app. Integrating PostHog enables analytics, custom events capture, feature flags, error tracking, and more.
 
@@ -20,16 +16,17 @@ Then, initialize PostHog where you'd like to use it. For example, here's how to
 
 app.py
 
-PostHog AI
-
 ```python
 from flask import Flask
 from posthog import Posthog
+
 app = Flask(__name__)
+
 posthog = Posthog(
     '<ph_project_token>',
     host='https://us.i.posthog.com',
 )
+
 @app.route('/api/dashboard', methods=['POST'])
 def api_dashboard():
     posthog.capture(
@@ -49,10 +46,9 @@ You can find your project token and instance address in [your project settings](
 >
 > Python
 >
-> PostHog AI
->
 > ```python
 > from posthog import new_context, identify_context, capture
+>
 > @app.get("/foo")
 > def foo(current_user: User = Depends(get_current_user)):
 >     with new_context(): # Set context at the top of a route
@@ -73,24 +69,27 @@ Then read the incoming headers in your Flask request handler. Tracing headers ar
 
 Python
 
-PostHog AI
-
 ```python
 from flask import request, session
 from posthog import identify_context, set_context_session, tag
+
 @app.route('/api/dashboard', methods=['POST'])
 def api_dashboard():
     with posthog.new_context(fresh=True):
         distinct_id = session.get('user_id') or request.headers.get('X-POSTHOG-DISTINCT-ID')
         if distinct_id:
             identify_context(str(distinct_id))
+
         session_id = request.headers.get('X-POSTHOG-SESSION-ID')
         if session_id:
             set_context_session(session_id)
+
         tag('$current_url', request.url)
         tag('$request_method', request.method)
         tag('$request_path', request.path)
+
         posthog.capture('dashboard_api_called')
+
     return '', 204
 ```
 
@@ -102,18 +101,19 @@ Flask has built-in error handlers. This means PostHog’s default exception auto
 
 Python
 
-PostHog AI
-
 ```python
 from flask import Flask, jsonify
 from posthog import Posthog
+
 app = Flask(__name__)
 posthog = Posthog('<ph_project_token>', host='https://us.i.posthog.com')
+
 @app.errorhandler(Exception)
 def handle_exception(e):
     # Capture methods, including capture_exception, return the UUID of the captured event,
     # which you can use to find specific errors users encountered
     event_id = posthog.capture_exception(e)
+
     # You can show the event ID to your user, and ask them to include it in bug reports
     response = jsonify({'message': str(e), 'error_id': event_id})
     response.status_code = 500