Skip to content

Metabase

Metabase is used for analytics and dashboards for product and sales data.

Notes

  • The service can be run via Docker Compose as metabase and optionally configured to use an external Postgres for persistence.
  • Replace https://metabase.lage-beauty.de/ with the actual domain or host when available.

Multi Repricer dashboard embed

The Analysis page (/analysis) embeds dashboard 3 through Metabase's official embed script and custom element. The frontend requests a short-lived, server-signed JWT from service-multi-repricer; the Metabase secret is never sent to the browser.

Sales forecast tables (plenty_sales_forecast, amazon_sales_forecast) are meant for Metabase questions — see Forecast Service. The Dashboard Forecast page (/forecast) is a lightweight UI over the same data.

Configure the service with:

  • METABASE_SITE_URL (for example https://metabase.lage-beauty.de)
  • METABASE_SECRET_KEY (the Metabase embedding secret — must be present in .env / Portainer stack env and passed into service-multi-repricer)
  • METABASE_DASHBOARD_ID (defaults to 3)
  • Embed JWT expiry is ACCESS_TOKEN_EXPIRE_MINUTES × 60 seconds (same lifetime as API access tokens)

Local docker-compose.yml loads these via env_file: .env and also lists them under service-multi-repricer.environment. Production Portainer compose injects them explicitly (it does not use a blanket env_file).