diff --git a/www/apps/cloud/app/billing-usage/page.mdx b/www/apps/cloud/app/billing-usage/page.mdx index a3aa3790d8..6a9eac0fab 100644 --- a/www/apps/cloud/app/billing-usage/page.mdx +++ b/www/apps/cloud/app/billing-usage/page.mdx @@ -114,7 +114,7 @@ You'll find two sections at the top of the Billing settings: You set your organization's plan when you sign up for Cloud. However, the plan may not be the best fit for your needs as your business grows. -If you want to change your plan or learn more about your plan's resources and limits, [contact support](#) for assistance. +If you want to change your plan or learn more about your plan's resources and limits, [contact support](../support/page.mdx) for assistance. --- @@ -149,4 +149,4 @@ If a payment for your organization's subscription fails, you'll receive a [notif The payment may fail for various reasons, such as insufficient funds, an expired card, or other issues with the payment method. Make sure to [update your payment method](#manage-payment-method) if needed. -If there are no issues with your payment method and the payment still fails, [contact support](#) for assistance. \ No newline at end of file +If there are no issues with your payment method and the payment still fails, [contact support](../support/page.mdx) for assistance. \ No newline at end of file diff --git a/www/apps/cloud/app/connect-storefront/page.mdx b/www/apps/cloud/app/connect-storefront/page.mdx new file mode 100644 index 0000000000..d582467289 --- /dev/null +++ b/www/apps/cloud/app/connect-storefront/page.mdx @@ -0,0 +1,70 @@ +export const metadata = { + title: `Cloud Best Practices: Connect Production Storefront`, +} + +# {metadata.title} + +In this guide, you'll learn how to allow your production storefront to send requests to your Medusa application deployed on Cloud. + +## Cloud and Storefront Hosting Overview + +Cloud only hosts Medusa applications. It doesn't support hosting your storefronts. Instead, you can use hosting providers like [Vercel](https://vercel.com/) to host your storefronts. + +If you're using the [Next.js Starter Storefront](!resources!/nextjs-starter), you can follow the [Deploy to Vercel](!resources!/deployment/storefront/vercel) guide to deploy your storefront. + +To send requests from your production storefront, you need to add some configurations both to it and the Medusa application deployed on Cloud. Otherwise, you'll receive an error when trying to send requests from the storefront. + +This guide lists the changes to make in your Medusa application and storefront to allow sending requests from the storefront. While the guide uses the Next.js Starter Storefront as an example, the steps are generally similar for any storefront. + +--- + +## Changes in Your Medusa Application + +To allow your production storefront to access your Medusa application on Cloud, you need to set two Cross-Origin Resource Sharing (CORS) environment variables in your Medusa application: + +- `STORE_CORS`: The URLs of storefronts that can access your Medusa server's `/store` API routes. This is a comma-separated list of URLs that is typically used as the value of the [http.storeCors](!docs!/learn/configurations/medusa-config#httpstorecors) configuration. +- `AUTH_CORS`: The URLs of the clients (storefront and admin) that can access the Medusa server's `/auth` API routes. This is a comma-separated list of URLs that is typically used as the value of the [http.authCors](!docs!/learn/configurations/medusa-config#httpauthcors) configuration. + +For example, if your storefront is hosted at `https://my-storefront.com`, you can [set the following environment variables in your production environment](../environments/page.mdx#add-environment-variables): + +```shell +STORE_CORS=https://my-storefront.com +AUTH_CORS=https://my-storefront.com +``` + +If you have multiple storefronts, you can add them to the list separated by commas: + +```shell +STORE_CORS=https://my-storefront.com,https://another-storefront.com +AUTH_CORS=https://my-storefront.com,https://another-storefront.com +``` + +After adding these environment variables, [redeploy the environment](../environments/page.mdx#redeploy-environment) to apply the changes. + +--- + +## Changes in Your Storefront + +To send requests from your storefront to your Medusa application on Cloud, you need to set two environment variables in the storefront: + +- `MEDUSA_BACKEND_URL`: The URL of your production Medusa application deployed on Cloud. For example, `https://my-project.medusajs.app`. + + + +If you copy the URL from a Cloud environment's dashboard, it may contain a `/app` suffix. Make sure to remove it from this variable. + + + +- `NEXT_PUBLIC_MEDUSA_PUBLISHABLE_KEY`: A publishable API key from your production Medusa application. You can [create or find an existing one using the Medusa Admin](!user-guide!/settings/developer/publishable-api-keys). + + + +These environment variable names are used by the Next.js Starter Storefront to connect to your Medusa application. If you're using a different storefront, you may need to set different environment variables. + + + +You can set these environment variables in your storefront's hosting provider. For example, if you're using Vercel, you can set them in the [Vercel dashboard](https://vercel.com/dashboard). + +Then, redeploy your storefront to apply the changes. + +With the [changes made in the Medusa application](#changes-in-your-medusa-application) and storefront, your storefront can now send requests to your Medusa application on Cloud. \ No newline at end of file diff --git a/www/apps/cloud/app/database/page.mdx b/www/apps/cloud/app/database/page.mdx index 6a74215ded..6a513e2eb6 100644 --- a/www/apps/cloud/app/database/page.mdx +++ b/www/apps/cloud/app/database/page.mdx @@ -28,7 +28,7 @@ Cloud automatically configures the database for your environments. So, you don't Cloud provides automatic backups for your environment databases. These backups are retained for 14 days and allow you to restore your database to a previous state, if needed. -If you need to restore a database backup, you can [contact support](#) to request a point-in-time recovery. This is useful if you accidentally delete data or need to revert changes made to the database. +If you need to restore a database backup, you can [contact support](../support/page.mdx) to request a point-in-time recovery. This is useful if you accidentally delete data or need to revert changes made to the database. --- diff --git a/www/apps/cloud/app/deployments/page.mdx b/www/apps/cloud/app/deployments/page.mdx index bfef937879..6298e7fbfd 100644 --- a/www/apps/cloud/app/deployments/page.mdx +++ b/www/apps/cloud/app/deployments/page.mdx @@ -25,9 +25,26 @@ For short-lived preview environments, Cloud creates a new environment and deploy --- +## Find Project Deployments + +You can find the deployments for a project in its dashboard. + +To find the deployments for a project: + +1. Make sure you're viewing the [correct organization's dashboard in Cloud](../organizations/page.mdx#switch-organization). +2. Click on the project you want to view its deployments. +3. Click on the "Deployments" tab in the project's dashboard. + +You'll find all deployments for the project's environments in the "Deployments" tab, sorted in descending order. For each deployment, you can see its branch, environment, status, and more. + +![Deployments tab in the project's dashboard](https://res.cloudinary.com/dza7lstvk/image/upload/v1750343899/Cloud/CleanShot_2025-06-19_at_17.37.45_2x_dwimzq.png) + +--- + + ## Find Environment Deployments -You can find the deployments for a project and its environments in the project and environment dashboards. +You can find the deployments for an environment in the project and environment dashboards. For example, to find the deployments for the Production environment: @@ -68,7 +85,7 @@ On the deployment details page, you'll find: 1. **Commit**: The commit that the deployment was created from. 2. **Status**: The current [status](#deployment-statuses-and-lifecycle) of the deployment. For example, "Live" or "Build Failed". 3. **Author**: The GitHub user who pushed the commit that created the deployment. -4. **Build Logs**: The logs from the build process. They are useful to understand why a deployment failed. Learn more in the [Logs](#) guide. +4. **Build Logs**: The logs from the build process. They are useful to understand why a deployment failed. Learn more in the [Logs](../logs/page.mdx) guide. ### Switch Between Deployments @@ -136,9 +153,9 @@ Where `my-project` is the subdomain you set either when [creating the project](. ### Access Deployment's Server through SSH -Cloud doesn't support SSH access to the server instance of a deployment. However, you can still access the server's [runtime and build logs](#) to debug issues in your application. +Cloud doesn't support SSH access to the server instance of a deployment. However, you can still access the server's [runtime and build logs](../logs/page.mdx) to debug issues in your application. -If this isn't sufficient for your use case, you can [contact support](#) to discuss alternatives. +If this isn't sufficient for your use case, you can [contact support](../support/page.mdx) to discuss alternatives. --- @@ -179,7 +196,7 @@ A deployment can have one of the following statuses: Build failed - The build process failed due to a build error. You can check the [build logs](#) to troubleshoot the issue. + The build process failed due to a build error. You can check the [build logs](../logs/page.mdx) to troubleshoot the issue. @@ -203,7 +220,7 @@ A deployment can have one of the following statuses: Deploy failed - The deployment failed during the deployment process. You can check the [Runtime Logs](#) to troubleshoot the issue. + The deployment failed during the deployment process. You can check the [Runtime Logs](../logs/page.mdx) to troubleshoot the issue. @@ -229,7 +246,7 @@ So, the lifecycle of a successful deployment is Building → Awaiting deployment -If a deployment is stuck at a status like "Building" or "Deploying" for a long time, [contact support](#) for assistance. +If a deployment is stuck at a status like "Building" or "Deploying" for a long time, [contact support](../support/page.mdx) for assistance. @@ -241,15 +258,15 @@ If a deployment is stuck at a status like "Building" or "Deploying" for a long t ### Troubleshooting Build Failures -If a deployment's status is "Build failed", you can check the [build logs](#) to understand why it failed. The build logs will show you the errors that occurred during the build process, which can help you fix the issue in your code. +If a deployment's status is "Build failed", you can check the [build logs](../logs/page.mdx) to understand why it failed. The build logs will show you the errors that occurred during the build process, which can help you fix the issue in your code. -You can also [contact support](#) for help with the issue, if necessary. +You can also [contact support](../support/page.mdx) for help with the issue, if necessary. ### Troubleshooting Deployment Failures -If a deployment's status is "Deploy failed", you can check the [runtime logs](#) to understand why it failed. The runtime logs will show you the errors that occurred during the deployment process, which can help you fix the issue in your code. +If a deployment's status is "Deploy failed", you can check the [runtime logs](../logs/page.mdx) to understand why it failed. The runtime logs will show you the errors that occurred during the deployment process, which can help you fix the issue in your code. -You can also [contact support](#) for help with the issue, if necessary. +You can also [contact support](../support/page.mdx) for help with the issue, if necessary. --- @@ -261,7 +278,7 @@ By redeploying a previous deployment, you revert or rollback the live version of -Redeploying a deployment will not revert database changes made in the latest deployment. If you need to revert database changes, [contact support](#) for assistance based on your use case. +Redeploying a deployment will not revert database changes made in the latest deployment. If you need to revert database changes, [contact support](../support/page.mdx) for assistance based on your use case. diff --git a/www/apps/cloud/app/draft-order-plugin/page.mdx b/www/apps/cloud/app/draft-order-plugin/page.mdx index c40b4e87e7..fe8cdd889a 100644 --- a/www/apps/cloud/app/draft-order-plugin/page.mdx +++ b/www/apps/cloud/app/draft-order-plugin/page.mdx @@ -34,4 +34,4 @@ The Draft Order Plugin provides the following features: The Draft Order Plugin is currently only available for Cloud users. If you're not a Cloud user, [learn how to get started](../page.mdx#sign-up-for-cloud). -Then, you can [contact support](#) for assistance in installing the Draft Order Plugin in your deployed Medusa application. \ No newline at end of file +Then, you can [contact support](../support/page.mdx) for assistance in installing the Draft Order Plugin in your deployed Medusa application. \ No newline at end of file diff --git a/www/apps/cloud/app/environments/page.mdx b/www/apps/cloud/app/environments/page.mdx index 0db963110c..d40cbe5113 100644 --- a/www/apps/cloud/app/environments/page.mdx +++ b/www/apps/cloud/app/environments/page.mdx @@ -119,6 +119,8 @@ After adding the environment variables, you need to redeploy the environment for 1. Go back to the environment's dashboard by clicking the "Overview" tab. 2. Click on the "Redeploy" button to redeploy the environment with the new environment variables. +This will redeploy the environment's live deployment with the new admin user credentials. + ![Redeploy button at the top right of the environment's dashboard](https://res.cloudinary.com/dza7lstvk/image/upload/v1750081204/Cloud/CleanShot_2025-06-16_at_16.39.44_2x_d3yij6.png) Then, wait for the deployment to finish. You can check its status in the "Deployments" section. Once it's deployed, you can [access the environment](#access-deployed-environment) using its URL. @@ -176,7 +178,7 @@ This will change the view to the selected environment, and you'll see its detail You can view build and runtime logs for an environment in the "Logs" section of the environment's dashboard. These logs help you debug issues in your application. -Learn more in the [Logs guide](#). +Learn more in the [Logs guide](../logs/page.mdx). --- @@ -293,7 +295,7 @@ In the environment's "Settings" tab, you can export a database dump of the envir You can also import a database dump to use existing data that you have, or to restore the environment to a previous state. -Learn more in the [Database](#) guide. +Learn more in the [Database](../database/page.mdx) guide. --- diff --git a/www/apps/cloud/app/loyalty-plugin/page.mdx b/www/apps/cloud/app/loyalty-plugin/page.mdx index 8584966692..b3dd765b98 100644 --- a/www/apps/cloud/app/loyalty-plugin/page.mdx +++ b/www/apps/cloud/app/loyalty-plugin/page.mdx @@ -36,4 +36,4 @@ The Loyalty Plugin provides the following features: The Loyalty Plugin is currently only available for Cloud users. If you're not a Cloud user, [learn how to get started](../page.mdx#sign-up-for-cloud). -Then, you can [contact support](#) for assistance in installing the Loyalty Plugin in your deployed Medusa application. \ No newline at end of file +Then, you can [contact support](../support/page.mdx) for assistance in installing the Loyalty Plugin in your deployed Medusa application. \ No newline at end of file diff --git a/www/apps/cloud/app/organizations/page.mdx b/www/apps/cloud/app/organizations/page.mdx index 108dd5d024..895b6fb2f1 100644 --- a/www/apps/cloud/app/organizations/page.mdx +++ b/www/apps/cloud/app/organizations/page.mdx @@ -200,6 +200,4 @@ To edit your profile's details: ## Manage Billing Details -{/* TODO add link */} - -Refer to the [Billing & Usage](#) guide to learn how to manage your organization's billing details, including payment methods, invoices, and usage. +Refer to the [Billing & Usage](../billing-usage/page.mdx) guide to learn how to manage your organization's billing details, including payment methods, invoices, and usage. diff --git a/www/apps/cloud/app/page.mdx b/www/apps/cloud/app/page.mdx index 751551567b..a43dc633a9 100644 --- a/www/apps/cloud/app/page.mdx +++ b/www/apps/cloud/app/page.mdx @@ -12,9 +12,9 @@ Welcome to the Cloud documentation. Learn about Cloud, its features, how to sign ## What is Cloud? -Cloud is Medusa's Platform-as-a-Service (PaaS) offering that facilitates deploying and operating your Medusa projects without having to worry about configuring, scaling, and maintaining its infrastructure and resources. +Cloud is Medusa's Platform-as-a-Service (PaaS) offering that facilitates deploying and operating your Medusa projects. You don't need to worry about configuring, scaling, and maintaining your application's infrastructure and resources. -By using Cloud, you only need to focus on building your commerce application that meets your business requirements. Cloud provides a seamless developer experience with features like direct deployments from GitHub, instant preview environments, and more. +By using Cloud, you only need to focus on building a commerce application that meets your business requirements. Cloud provides a seamless developer experience with features like direct deployments from GitHub, instant preview environments, and more. --- @@ -50,17 +50,11 @@ You can also contact a [Medusa Expert](https://medusajs.com/experts/) to help yo Cloud can only host Medusa servers and admin dashboards. To host your storefront, you can use hosting providers like Vercel. -{/* TODO Add link */} - -Learn more about connecting your storefront to your Medusa server deployed on Cloud in the [Connecting Storefront](#) guide. +Learn more in the [Connect Production Storefront](./connect-storefront/page.mdx) guide. ### What resources does Cloud provide? -Cloud provides fully-managed resources like PostgreSQL, Redis, S3, and more. You don't need to configure or maintain them. - -{/* TODO Add link to resources guide */} - -Learn more about the resources provided by Cloud in the [Resources](#) guide. +Cloud fully-manages your [PostgreSQL databases](./database/page.mdx), [Redis instances](./redis/page.mdx), and [S3 buckets](./s3/page.mdx). You don't need to configure or maintain them. ### Do I own my code and data for my Medusa project on Cloud? diff --git a/www/apps/cloud/app/projects/page.mdx b/www/apps/cloud/app/projects/page.mdx index 51695e2a23..8d815d5b57 100644 --- a/www/apps/cloud/app/projects/page.mdx +++ b/www/apps/cloud/app/projects/page.mdx @@ -14,7 +14,7 @@ A project is the collection of resources, environments, deployments, and setting To deploy a Medusa application to the Cloud, you create a project for it. Cloud will automatically set up and configure the necessary resources in the project to run the application, such as PostgreSQL, Redis, and S3. -Each project can have multiple environments, such as production and staging. These environments allow you to test changes before pushing them live to users. You can learn more in the [Environments documentation](#). +Each project can have multiple environments, such as production and staging. These environments allow you to test changes before pushing them live to users. You can learn more in the [Environments documentation](../environments/page.mdx). --- @@ -29,7 +29,7 @@ Before creating a project, ensure you have: - A Medusa application whose codebase is hosted in a GitHub repository. - If you don't have a Medusa application yet, refer to the [Installation](!docs!/learn/installation) guide to set up a new Medusa application. - A Cloud account with a valid plan that allows creating more projects. - - If you've exceeded the number of projects limit for your plan, you can [contact support to upgrade your plan](#). + - If you've exceeded the number of projects limit for your plan, you can [contact support](../support/page.mdx) to upgrade your plan. #### Medusa Application Configurations @@ -70,7 +70,7 @@ To create a project: 7. You can optionally change the "Build and project" settings by expanding its section: - Select a region to deploy the project. For better performance, choose a region that's closer to your target users. The region can't be changed later. - - If you don't find the region you need, you can [contact support](#) to request it. + - If you don't find the region you need, you can [contact support](../support/page.mdx) to request it. - If your project is in a monorepo, you can specify the path to the Medusa project in the repository. Otherwise, leave it empty. - You can change the email and password for the admin user created for the project. These are the credentials you'll use to access the Medusa Admin. @@ -106,10 +106,8 @@ Once the project is created and deployed, you'll receive a notification in the C If you encounter any issues while creating a project: -{/* TODO: add links */} - -- [Check the build and runtime logs of the project's production deployment](#). -- [Contact support for help](#). +- [Check the build and runtime logs of the project's production deployment](../logs/page.mdx). +- [Contact support for help](../support/page.mdx). --- @@ -139,7 +137,7 @@ On the project's dashboard, you can view the following details: ![The project dashboard with the details of a project](https://res.cloudinary.com/dza7lstvk/image/upload/v1749743078/Cloud/CleanShot_2025-06-12_at_18.42.54_2x_rin0pw.png) 1. **Region**: The region where the project is deployed. You'll find it below the project name. -2. **Environments**: The environments for the project are shown as cards. By default, you'll find Production and Previews environments. You can learn more about environments in the [Environments documentation](#). +2. **Environments**: The environments for the project are shown as cards. By default, you'll find Production and Previews environments. You can learn more about environments in the [Environments](../environments/page.mdx) guide. - The Production environment is the live environment where your Medusa application is deployed and clients connect to. - The Previews environments are created whenever you create a pull request in the linked GitHub repository. They allow you to preview changes before merging them into the main branch. 3. **Production URL**: The URL of the project's production deployment. You'll find it in the "Production" card under the title. Clicking it will open the production Medusa Admin in a new tab. @@ -165,7 +163,7 @@ This will change the view to the selected project, and you'll see its details, e To view the deployments of a project, click on the "Deployments" tab in the project's dashboard. This will show you a list of all deployments for the project, including their status, environment, and how long the deployment took. -Learn more in the [Deployments documentation](#). +Learn more in the [Deployments](../deployments/page.mdx) guide. --- @@ -187,7 +185,7 @@ To edit a project's general details: You can also edit the "Previews" settings of a project from the "Settings" tab, which are general settings related to Previews environments. -Learn more in the [Environments documentation](#). +Learn more in the [Environments](../environments/page.mdx) guide. --- diff --git a/www/apps/cloud/app/redis/page.mdx b/www/apps/cloud/app/redis/page.mdx index f4ccae7eb5..a2cf8732a0 100644 --- a/www/apps/cloud/app/redis/page.mdx +++ b/www/apps/cloud/app/redis/page.mdx @@ -29,7 +29,7 @@ So, you don't need to configure any of these modules and providers or set up Red -If you're using a Medusa version before v2.7.0, [contact support](#) for assistance in configuring the Redis modules. +If you're using a Medusa version before v2.7.0, [contact support](../support/page.mdx) for assistance in configuring the Redis modules. diff --git a/www/apps/cloud/app/s3/page.mdx b/www/apps/cloud/app/s3/page.mdx index 557005383e..737f5ebb39 100644 --- a/www/apps/cloud/app/s3/page.mdx +++ b/www/apps/cloud/app/s3/page.mdx @@ -26,7 +26,7 @@ So, you don't need to configure the S3 File Module Provider or set up S3 manuall -If you're using a Medusa version before v2.7.0, [contact support](#) for assistance in configuring the S3 File Module Provider. +If you're using a Medusa version before v2.7.0, [contact support](../support/page.mdx) for assistance in configuring the S3 File Module Provider. diff --git a/www/apps/cloud/generated/edit-dates.mjs b/www/apps/cloud/generated/edit-dates.mjs index 0cef367b5d..8500cfdb44 100644 --- a/www/apps/cloud/generated/edit-dates.mjs +++ b/www/apps/cloud/generated/edit-dates.mjs @@ -1,18 +1,19 @@ export const generatedEditDates = { - "app/page.mdx": "2025-06-12T12:31:48.681Z", + "app/page.mdx": "2025-06-19T14:17:00.893Z", "app/organization/page.mdx": "2025-06-12T14:43:20.772Z", - "app/projects/page.mdx": "2025-06-17T11:20:16.174Z", - "app/environments/page.mdx": "2025-06-17T14:29:55.288Z", - "app/deployments/page.mdx": "2025-06-17T11:17:03.236Z", - "app/organizations/page.mdx": "2025-06-17T10:48:50.969Z", + "app/projects/page.mdx": "2025-06-19T14:17:06.679Z", + "app/environments/page.mdx": "2025-06-19T14:15:00.389Z", + "app/deployments/page.mdx": "2025-06-19T14:14:31.740Z", + "app/organizations/page.mdx": "2025-06-19T14:15:13.990Z", "app/notifications/page.mdx": "2025-06-17T12:29:18.819Z", - "app/database/page.mdx": "2025-06-17T14:34:57.104Z", - "app/redis/page.mdx": "2025-06-18T06:50:30.705Z", - "app/s3/page.mdx": "2025-06-18T07:16:14.453Z", - "app/draft-order-plugin/page.mdx": "2025-06-18T08:32:21.263Z", - "app/loyalty-plugin/page.mdx": "2025-06-18T08:28:51.756Z", - "app/billing-usage/page.mdx": "2025-06-18T10:35:56.993Z", + "app/database/page.mdx": "2025-06-19T14:13:32.800Z", + "app/redis/page.mdx": "2025-06-19T14:16:06.488Z", + "app/s3/page.mdx": "2025-06-19T14:16:11.227Z", + "app/draft-order-plugin/page.mdx": "2025-06-19T14:14:49.500Z", + "app/loyalty-plugin/page.mdx": "2025-06-19T14:15:04.352Z", + "app/billing-usage/page.mdx": "2025-06-19T14:13:29.533Z", "app/logs/page.mdx": "2025-06-19T07:44:38.336Z", "app/support/page.mdx": "2025-06-19T11:18:37.253Z", - "app/update-medusa/page.mdx": "2025-06-19T11:18:42.545Z" + "app/update-medusa/page.mdx": "2025-06-19T11:18:42.545Z", + "app/connect-storefront/page.mdx": "2025-06-19T14:13:06.812Z" } \ No newline at end of file diff --git a/www/apps/cloud/generated/sidebar.mjs b/www/apps/cloud/generated/sidebar.mjs index fcb3fa9633..e3f0b0684b 100644 --- a/www/apps/cloud/generated/sidebar.mjs +++ b/www/apps/cloud/generated/sidebar.mjs @@ -177,6 +177,14 @@ export const generatedSidebars = [ "title": "Update Medusa", "path": "/update-medusa", "children": [] + }, + { + "loaded": true, + "isPathHref": true, + "type": "link", + "title": "Connect Storefront", + "path": "/connect-storefront", + "children": [] } ] } diff --git a/www/apps/cloud/sidebar.mjs b/www/apps/cloud/sidebar.mjs index 7af20a6c00..9bfec16b17 100644 --- a/www/apps/cloud/sidebar.mjs +++ b/www/apps/cloud/sidebar.mjs @@ -122,6 +122,11 @@ export const sidebar = [ title: "Update Medusa", path: "/update-medusa", }, + { + type: "link", + title: "Connect Storefront", + path: "/connect-storefront", + }, ], }, ],