Skip to content

Align Hub env names: PostHog uses POSTHOG_* not ENDATIX_ #960

Description

@PeterMarinov

Goal

Hub env names should be predictable: ENDATIX_ only for Endatix API / product identity; integrations use a domain stem (POSTHOG_*, STORAGE_*, AUTH_*). Public vs secret is which reader (readPublicEndatixEnv vs server-only), not the ENDATIX_ prefix. NEXT_PUBLIC_* stays forbidden except NEXT_PUBLIC_BASE_PATH.

Implementation Notes

ENDATIX_POSTHOG_* exists only because we migrated off NEXT_PUBLIC_* and reused ENDATIX_ as “request-time public”. That collides with ENABLE_POSTHOG_ADAPTER and with STORAGE_ / AUTH_ style.

This issue (churn allowed — Hub is the only consumer):

  • ENDATIX_POSTHOG_KEY|HOST|UI_HOSTPOSTHOG_KEY|HOST|UI_HOST
  • ENABLE_POSTHOG_ADAPTERPOSTHOG_ADAPTER (true/false)
  • SWA workflow, sandbox-deploy, Helm, .env.example, Environment admin labels, readPublicEndatixEnv, flag adapter
  • Document the convention in hub/AGENTS.md (Configuration section)

Exceptions (do not rename in this issue): ENDATIX_BASE_URL / API_URL / API_PREFIX; ENDATIX_ENABLE_EXTENSIONS; ENDATIX_SURVEY_LICENSE_KEY; ENDATIX_RECAPTCHA_SITE_KEY; ENDATIX_IS_DEBUG_MODE; ENDATIX_SUBMITTER_*; ENDATIX_RESOLVED_*; NEXT_PUBLIC_BASE_PATH; Auth.js AUTH_*; FLAG_*.

No dual-name fallback.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    🎁 hosting-and-deploymentFeature Area is Hosting & DeploymentdocumentationImprovements or additions to documentationendatix-hubRequires changes in the Endatix Hub part of the repotech-debtTechnical debt. Addressing this will address known issue or opportunity to improve the codebase

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions