Configure DataHub for Payne

Payne’s local-live profile includes DataHub Core 1.6.0, the self-hosted DataHub MCP server, the official showcase-ecommerce datapack, and a checked-in additive finance retirement overlay.

Use the official DataHub quickstart  for DataHub host requirements and the official DataHub MCP Server guide  for the MCP interface Payne discovers. Payne’s commands below remain the source of truth for this repository’s pinned local profile.

Start and verify

1. Copy .env.local-live.example to .env.local-live and replace the local-only secrets if the stack will be shared.
2. Run pnpm local:up from the repository root.
3. Wait for Payne local-live is ready at http://localhost:3000.
4. Open Health. The DataHub, datapack, scenario, and MCP milestones must be verified before you proceed.
5. Open Connection and run the connection check. Required reads are core metadata, schema, downstream lineage, and ownership/domains.

Startup uses the native local DataHub account to mint separate review and application tokens. PAYNE_DATAHUB_TOKEN supplies the current catalog actor and read-after-write reads. PAYNE_DATAHUB_WRITE_TOKEN is supplied only to the worker from the separately provisioned bootstrap token.

If a discovered MCP capability is absent, Payne records the limitation rather than treating unavailable evidence as an empty result. See Connection limitations.