Fluent Commerce Logo
Docs

CI/CD Using Mystique UI Bundles

Essential knowledgeCore knowledge to understand Fluent Commerce

Changed on:

9 Nov 2026

Overview

[Warning: empty required content area]

Key points

[Warning: empty required content area]
Custom Mystique components are built into a static JavaScript bundle, hosted at a URL, and loaded by the Fluent web apps through a plugin reference in the Mystique manifest. In CI/CD terms this is a simple front-end pipeline:`lint → test → build → upload to static hosting → update manifest reference`

Pipeline steps

`publish-mystique.sh` uploads `dist/` to your hosting provider. Its contents depend on the provider (S3 + CloudFront, Azure Static Web Apps, Vercel, Netlify, ...). Whichever you use:
  • Publish to a versioned path (`/acme-mystique-plugin/1.4.0/`) and never overwrite a published version. The manifest then points at an immutable bundle, and rolling back means changing a URL.
  • Keep the host per environment, or at least the path. A dev build must never be what UAT or production loads.
  • Allow the host in the security headers. The bundle's origin must be permitted by the Mystique Content-Security-Policy (`fc.mystique.security.headers`). Change it through the pipeline like any other setting.
  • Keep secrets out of the bundle. Anything in it is public.

Manifests

Treat Mystique manifests as source, like workflows. Keep them in the repository, deploy them from the pipeline as settings, and update the bundle URL in the same release that publishes the bundle. A manifest edited by hand in an environment is drift (see Verification).