Skip to main content
Version: next

Set up the Gezy backend

The CMS stores its pages and media through your connector. With the Gezy flavour, a few prerequisites must be in place on the Gezy side before content managers can edit pages.

Enabling cms("gezy") in your front-commerce.config.ts is only the Front-Commerce side of the setup (see the CMS overview). The Gezy backend must also be configured for the editor and publishing to work.

Register the extension after Gezy​

cms("gezy") reads the Gezy connector's services when the server starts — to resolve content storage and the media library. It must therefore be registered after gezy() in your extensions array:

front-commerce.config.ts
export default defineConfig({
  extensions: [
    gezy({ storesConfig }),
    cms("gezy"),
  ],
  // …
});

A Gezy connector that is itself correctly configured is a prerequisite — see Set up the Gezy extension and its environment variables.

Enable the CMS API on your Gezy instance​

The CMS reads and writes content through Gezy's CMS API — the page store and the media library. Your Gezy instance must expose this API for the environment you connect to. If pages fail to load or the media library is empty, confirm with your Gezy administrator that the CMS capability is enabled on that instance.

Grant the cms/events permission​

Editing and publishing are gated by the cms/events permission. The role of the user who contributes must be granted cms/events on the Gezy side; Front-Commerce maps it to the internal admin.cms permission that controls the Page Editor and the Publish action.

Without this permission the editor and the publish action stay unavailable, even when contribution mode is enabled.

Media storage​

By default, media is served from the Gezy media library. For local development against a backend that has no media API, you can force the built-in filesystem backend instead:

.env
FRONT_COMMERCE_CMS_MEDIA_DANGEROUSLY_FORCE_FILESYSTEM=true

As its name suggests, this is a development-only escape hatch: it ignores the connector's media backend entirely and stores files on the local filesystem.

Next​