Files
medusa-store/docs/content/plugins/cms/strapi.md
Shahed Nasser 1decaa27c7 docs: publish restructure (#3496)
* docs: added features and guides overview page

* added image

* added version 2

* added version 3

* added version 4

* docs: implemented new color scheme

* docs: redesigned sidebar (#3193)

* docs: redesigned navbar for restructure (#3199)

* docs: redesigned footer (#3209)

* docs: redesigned cards (#3230)

* docs: redesigned admonitions (#3231)

* docs: redesign announcement bar (#3236)

* docs: redesigned large cards (#3239)

* docs: redesigned code blocks (#3253)

* docs: redesigned search modal and page (#3264)

* docs: redesigned doc footer (#3268)

* docs: added new sidebars + refactored css and assets (#3279)

* docs: redesigned api reference sidebar

* docs: refactored css

* docs: added code tabs transition

* docs: added new sidebars

* removed unused assets

* remove unusued assets

* Fix deploy errors

* fix incorrect link

* docs: fixed code responsivity + missing icons (#3283)

* docs: changed icons (#3296)

* docs: design fixes to the sidebar (#3297)

* redesign fixes

* docs: small design fixes

* docs: several design fixes after restructure (#3299)

* docs: bordered icon fixes

* docs: desgin fixes

* fixes to code blocks and sidebar scroll

* design adjustments

* docs: restructured homepage (#3305)

* docs: restructured homepage

* design fixes

* fixed core concepts icon

* docs: added core concepts page (#3318)

* docs: restructured homepage

* design fixes

* docs: added core concepts page

* changed text of different components

* docs: added architecture link

* added missing prop for user guide

* docs: added regions overview page (#3327)

* docs: added regions overview

* moved region pages to new structure

* docs: fixed description of regions architecture page

* small changes

* small fix

* docs: added customers overview page (#3331)

* docs: added regions overview

* moved region pages to new structure

* docs: fixed description of regions architecture page

* small changes

* small fix

* docs: added customers overview page

* fix link

* resolve link issues

* docs: updated regions architecture image

* docs: second-iteration fixes (#3347)

* docs: redesigned document

* design fixes

* docs: added products overview page (#3354)

* docs: added carts overview page (#3363)

* docs: added orders overview (#3364)

* docs: added orders overview

* added links in overview

* docs: added vercel redirects

* docs: added soon badge for cards (#3389)

* docs: resolved feedback changes + organized troubleshooting pages (#3409)

* docs: resolved feedback changes

* added extra line

* docs: changed icons for restructure (#3421)

* docs: added taxes overview page (#3422)

* docs: added taxes overview page

* docs: fix sidebar label

* added link to taxes overview page

* fixed link

* docs: fixed sidebar scroll (#3429)

* docs: added discounts overview (#3432)

* docs: added discounts overview

* fixed links

* docs: added gift cards overview (#3433)

* docs: added price lists overview page (#3440)

* docs: added price lists overview page

* fixed links

* docs: added sales channels overview page (#3441)

* docs: added sales overview page

* fixed links

* docs: added users overview (#3443)

* docs: fixed sidebar border height (#3444)

* docs: fixed sidebar border height

* fixed svg markup

* docs: added possible solutions to feedback component (#3449)

* docs: added several overview pages + restructured files (#3463)

* docs: added several overview pages

* fixed links

* docs: added feature flags + PAK overview pages (#3464)

* docs: added feature flags + PAK overview pages

* fixed links

* fix link

* fix link

* fixed links colors

* docs: added strategies overview page (#3468)

* docs: automated upgrade guide (#3470)

* docs: automated upgrade guide

* fixed vercel redirect

* docs: restructured files in docs codebase (#3475)

* docs: restructured files

* docs: fixed eslint exception

* docs: finished restructure loose-ends (#3493)

* fixed uses of backend

* docs: finished loose ends

* eslint fixes

* fixed links

* merged master

* added update instructions for v1.7.12
2023-03-16 17:03:10 +02:00

7.6 KiB
Raw Blame History

description, addHowToData
description addHowToData
Learn how to integrate Strapi with the Medusa backend. Learn how to install the plugin and test two-way sync between the ecommerce and CMS services. true

Strapi

In this document, youll learn how to integrate Strapi with Medusa to add rich Content Management System (CMS) functionalities.

:::info

This plugin is a community plugin and is not managed by the official Medusa team. At the moment, it supports v4 of Strapi.

:::

Overview

Strapi is an open source headless CMS service that allows developers to have complete control over their content models. It can be integrated into many other frameworks, including Medusa.

By integrating Strapi to Medusa, you can benefit from powerful features in your ecommerce store including detailed product CMS details, two-way sync, an easy-to-use interface to use for static content and pages, and much more.


Prerequisites

Medusa CLI

Medusas CLI tool is required to set up a new Medusa backend.

Redis

Redis is required for the Strapi plugin to work as expected on your Medusa backend. If you dont have it installed, you can learn how to install it in this documentation.


Create Strapi Project

The first step is to create a Strapi project using the Medusa template:

npx create-strapi-app strapi-medusa --template shahednasser/strapi-medusa-template

This creates the Strapi project in the directory strapi-medusa.

Once the installation is finished, the Strapi development backend will run on localhost:1337. A new page will also open in your default browser to create a new admin user and log in.

Create User Form in Strapi

Once you log in, you can access the Strapi dashboard.

Create a Strapi User

The Strapi plugin in Medusa requires the credentials of a Strapi user. To create a new user, go to Content Manager, then choose User under Collection Types.

Showing the users under Content Manager

Click on the Create new entry button at the top right. This opens a new form to enter the users details.

Create User Form on Strapi

Enter the users username, email, and password. Once youre done, click on the Save button at the top right.


Modify Permissions

By default, created users have the “Authenticated” role. Before you start using the Strapi plugin on your Medusa backend, you must modify this roles permissions to allow making changes to Medusas models in Strapi.

On your Strapi dashboard, go to Settings → Roles → Authenticated. Then, under the Permissions section, expand the accordion of each content model type and check the Select All checkbox.

An example of modifying permissions on the Product content type

Once youre done, click the Save button at the top right.


Create Medusa Backend

:::note

You can use the Strapi plugin on an existing Medusa backend, however, existing data (such as existing products) will not be imported. Only newer data will be imported.

:::

To create your Medusa backend, run the following command:

medusa new medusa-backend --seed

The --seed flag creates an SQLite database and seeds it with some demo data.

Configure your Backend

Once the command is done executing, change to the newly created medusa-backend directory. Then, in medusa-config.js, change the exported object at the end of the file to enable Redis:

module.exports = {
  projectConfig: {
    redis_url: REDIS_URL,
    // ...
  },
  // ...
}

This uses the default Redis configurations. If you want to learn more about configuring Redis, check out this documentation.

:::tip

It is also recommended to use PostgreSQL for an optimal experience, however, it is not required. Learn how to install and configure it on your Medusa backend.

:::


Install the Strapi Plugin

In the directory of your Medusa backend, run the following command to install the Strapi plugin:

npm install medusa-plugin-strapi

Then, add the following environment variables:

STRAPI_USER=<STRAPI_IDENTIFIER>
STRAPI_PASSWORD=<STRAPI_PASSWORD>
STRAPI_PROTOCOL=http # Optional
STRAPI_URL=<STRAPI_URL> # Optional
STRAPI_PORT=<STRAPI_PORT> # Optional

Where:

  • <STRAPI_IDENTIFIER> is either the email address or username of the user you created in the previous step.
  • <STRAPI_PASSWORD> is the password of the user you created in the previous step.
  • <STRAPI_PROTOCOL> is the protocol of your Strapi backend. If youre using a local Strapi backend, set this to http. The default value is https.
  • <STRAPI_URL> is the URL of your Strapi backend. By default, the URL is localhost.
  • <STRAPI_PORT> is the port the Strapi backend runs on. By default, the port is 1337.

Finally, open medusa-config.js and add the following new item to the plugins array:

const plugins = [
  // ...
  {
    resolve: `medusa-plugin-strapi`,
    options: {
      strapi_medusa_user: process.env.STRAPI_USER,
      strapi_medusa_password: process.env.STRAPI_PASSWORD,
      strapi_url: process.env.STRAPI_URL, // optional
      strapi_port: process.env.STRAPI_PORT, // optional
      strapi_protocol: process.env.STRAPI_PROTOCOL, // optional
    },
  },
]

Run Medusa Backend

Make sure the Strapi backend is still running. If not, you can run the following command to run the Strapi backend in the directory of the Strapi project:

npm run develop

Then, in the directory of your Medusa backend, run the following command to start the Medusa backend:

npm run start

Once you start your Medusa backend, if you ran the --seed command when you created your Medusa backend, youll see that product.created events have been triggered along with similar events. This will update Strapi with the products you seeded.


Test Two-Way Sync

This plugin ensures a two-way sync between the Medusa backend and the Strapi backend. So, if you update data on Strapi, it will be reflected on your Medusa backend, and vice-versa.

Update Products on Strapi

Try updating any products on Strapi by going to Content Manager → Products and choosing a product from the list. Then, make changes to the product and click Save. If you view the products on your backend now, either using the REST APIs or using the Medusa Admin, youll see that the product has been updated.

Update Products on Medusa

If you try to update products on Medusa either using the REST APIs or using the Medusa Admin, youll see that the product is also updated on Strapi.


See Also