asyavee/medusa-store
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: general changes to Cloud docs (#13616)

Browse Source 
* docs: document self serve

* docs: Cloud docs changes

* vale fixes

* vale error fix

* fixes

* added new sections

* generate
This commit is contained in:
Shahed Nasser
2025-09-30 18:37:04 +03:00
committed by GitHub
parent 70d855bd1b
commit a1dd2de0de
20 changed files with 538 additions and 491 deletions
Download Patch File Download Diff File Expand all files Collapse all files
www/apps/book/app/learn/build/page.mdx
+6 -2
View File
@@ -8,6 +8,12 @@ In this chapter, you'll learn how to create a production build of your Medusa ap
Next chapters explain how to deploy the Medusa application.
<Note title="Deploy with Cloud" type="success">
The below instructions are useful for self-hosting your Medusa application. You can also use [Cloud](!cloud!) to deploy and manage your Medusa application without worrying about infrastructure. Medusa will handle the configurations, deployment, and scaling for you.
</Note>
## build Command
The Medusa CLI tool provides a [build](!resources!/medusa-cli/commands/build) command that creates a standalone build of the Medusa application that:
@@ -117,5 +123,3 @@ Make sure to remove the `projectConfig.cookieOptions` configuration once you're
## Deploying Production Build
The next chapter covers how to deploy the production build.
You can also refer to the [deployment how-to guides](!resources!/deployment) for platform-specific deployment instructions.
www/apps/book/app/learn/deployment/general/page.mdx
+3 -7
View File
@@ -6,17 +6,13 @@ export const metadata = {
# {metadata.title}
In this document, you'll learn the general steps to deploy your Medusa application. How you apply these steps depend on your chosen hosting provider or platform.
Find how-to guides for specific platforms in [this documentation](!resources!/deployment).
In this guide, you'll learn the general steps to deploy your Medusa application. How you apply these steps depend on your chosen hosting provider or platform.
<Note title="Deploy with Cloud" type="success">
Want Medusa to manage and maintain your infrastructure? [Sign up and learn more about Cloud](!cloud!)
Before deciding to self-host your Medusa application, consider reading the [Cloud vs. Self-Hosting comparison guide](!cloud!/comparison). By using Cloud, you can avoid the complexities and challenges of self-hosting, while benefiting from automated deployment, scaling, and maintenance.
Cloud is our managed services offering that makes deploying and operating Medusa applications possible without having to worry about configuring, scaling, and maintaining infrastructure. Cloud hosts your server, Admin dashboard, database, and Redis instance.
With Cloud, you maintain full customization control as you deploy your own modules and customizations directly from GitHub:
With Cloud, you also maintain full customization control as you deploy your own modules and customizations directly from GitHub:
- Push to deploy.
- Multiple testing environments.
www/apps/book/app/learn/deployment/page.mdx
+17 -2
View File
@@ -6,6 +6,21 @@ export const metadata = {
In this chapter, you’ll learn the general approach to deploying the Medusa application.
<Note title="Deploy with Cloud" type="success">
Want Medusa to manage and maintain your infrastructure? [Sign up and learn more about Cloud](!cloud!)
Cloud is our managed services offering that makes deploying and operating Medusa applications possible without having to worry about configuring, scaling, and maintaining infrastructure. Cloud hosts your server, Admin dashboard, database, and Redis instance.
With Cloud, you maintain full customization control as you deploy your own modules and customizations directly from GitHub:
- Push to deploy.
- Multiple testing environments.
- Preview environments for new PRs.
- Test on production-like data.
</Note>
## Medusa Project Components
A standard Medusa project is made up of:
@@ -23,11 +38,11 @@ You deploy the Medusa application, with the server and admin, separately from th
You must deploy the Medusa application before the storefront, as it connects to the server and won’t work without a deployed Medusa server URL.
The Medusa application must be deployed to a hosting provider supporting Node.js server deployments, such as Railway, DigitalOcean, AWS, Heroku, etc…
The Medusa application must be deployed to a hosting provider supporting Node.js server deployments.
![Medusa server deployment infrastructure diagram illustrating the backend services ecosystem: the Node.js Medusa server connected to essential services including PostgreSQL database for data storage, and Redis for caching and session management](https://res.cloudinary.com/dza7lstvk/image/upload/v1708600972/Medusa%20Book/backend_deployment_pgexo3.jpg)
Your server connects to a PostgreSQL database, Redis, and other services relevant for your setup. Most hosting providers support deploying and managing these databases along with your Medusa server (such as Railway and DigitalOcean).
Your server connects to a PostgreSQL database, Redis, and other services relevant for your setup. Most hosting providers support deploying and managing these databases along with your Medusa server.
When you deploy your Medusa application, you also deploy the Medusa Admin. For optimal experience, your hosting provider and plan must offer at least 2GB of RAM.
www/apps/book/generated/edit-dates.mjs
+3 -3
View File
@@ -1,7 +1,7 @@
export const generatedEditDates = {
"app/learn/fundamentals/scheduled-jobs/page.mdx": "2025-07-25T15:56:17.926Z",
"app/learn/fundamentals/workflows/page.mdx": "2024-12-09T14:45:17.837Z",
"app/learn/deployment/page.mdx": "2025-07-18T15:25:33.249Z",
"app/learn/deployment/page.mdx": "2025-09-29T10:25:29.915Z",
"app/learn/page.mdx": "2025-06-27T11:39:15.941Z",
"app/learn/fundamentals/modules/commerce-modules/page.mdx": "2025-04-17T08:51:32.723Z",
"app/learn/fundamentals/workflows/retry-failed-steps/page.mdx": "2025-09-15T09:38:18.299Z",
@@ -93,8 +93,8 @@ export const generatedEditDates = {
"app/learn/fundamentals/data-models/infer-type/page.mdx": "2025-03-18T07:41:01.936Z",
"app/learn/fundamentals/custom-cli-scripts/seed-data/page.mdx": "2025-09-15T16:02:51.362Z",
"app/learn/fundamentals/environment-variables/page.mdx": "2025-05-26T15:06:07.800Z",
"app/learn/build/page.mdx": "2025-09-30T06:10:46.850Z",
"app/learn/deployment/general/page.mdx": "2025-09-01T06:21:43.760Z",
"app/learn/build/page.mdx": "2025-09-30T06:14:50.101Z",
"app/learn/deployment/general/page.mdx": "2025-09-29T10:21:24.768Z",
"app/learn/fundamentals/workflows/multiple-step-usage/page.mdx": "2025-08-01T14:59:59.501Z",
"app/learn/installation/page.mdx": "2025-07-23T14:28:50.404Z",
"app/learn/fundamentals/data-models/check-constraints/page.mdx": "2025-07-25T13:50:21.065Z",
www/apps/book/public/llms-full.txt
+18 -11
View File
@@ -6,6 +6,8 @@ In this chapter, you'll learn how to create a production build of your Medusa ap
Next chapters explain how to deploy the Medusa application.
The below instructions are useful for self-hosting your Medusa application. You can also use [Cloud](https://docs.medusajs.com/cloud/index.html.md) to deploy and manage your Medusa application without worrying about infrastructure. Medusa will handle the configurations, deployment, and scaling for you.
## build Command
The Medusa CLI tool provides a [build](https://docs.medusajs.com/resources/medusa-cli/commands/build/index.html.md) command that creates a standalone build of the Medusa application that:
@@ -104,8 +106,6 @@ Make sure to remove the `projectConfig.cookieOptions` configuration once you're
The next chapter covers how to deploy the production build.
You can also refer to the [deployment how-to guides](https://docs.medusajs.com/resources/deployment/index.html.md) for platform-specific deployment instructions.
# Medusa Application Configuration
@@ -6080,15 +6080,11 @@ The next chapters explain how to use the testing tools provided by `@medusajs/te
# General Medusa Application Deployment Guide
In this document, you'll learn the general steps to deploy your Medusa application. How you apply these steps depend on your chosen hosting provider or platform.
In this guide, you'll learn the general steps to deploy your Medusa application. How you apply these steps depend on your chosen hosting provider or platform.
Find how-to guides for specific platforms in [this documentation](https://docs.medusajs.com/resources/deployment/index.html.md).
Before deciding to self-host your Medusa application, consider reading the [Cloud vs. Self-Hosting comparison guide](https://docs.medusajs.com/cloud/comparison/index.html.md). By using Cloud, you can avoid the complexities and challenges of self-hosting, while benefiting from automated deployment, scaling, and maintenance.
Want Medusa to manage and maintain your infrastructure? [Sign up and learn more about Cloud](https://docs.medusajs.com/cloud/index.html.md)
Cloud is our managed services offering that makes deploying and operating Medusa applications possible without having to worry about configuring, scaling, and maintaining infrastructure. Cloud hosts your server, Admin dashboard, database, and Redis instance.
With Cloud, you maintain full customization control as you deploy your own modules and customizations directly from GitHub:
With Cloud, you also maintain full customization control as you deploy your own modules and customizations directly from GitHub:
- Push to deploy.
- Multiple testing environments.
@@ -6408,6 +6404,17 @@ You can use these credentials to log into the Medusa Admin dashboard.
In this chapter, you’ll learn the general approach to deploying the Medusa application.
Want Medusa to manage and maintain your infrastructure? [Sign up and learn more about Cloud](https://docs.medusajs.com/cloud/index.html.md)
Cloud is our managed services offering that makes deploying and operating Medusa applications possible without having to worry about configuring, scaling, and maintaining infrastructure. Cloud hosts your server, Admin dashboard, database, and Redis instance.
With Cloud, you maintain full customization control as you deploy your own modules and customizations directly from GitHub:
- Push to deploy.
- Multiple testing environments.
- Preview environments for new PRs.
- Test on production-like data.
## Medusa Project Components
A standard Medusa project is made up of:
@@ -6425,11 +6432,11 @@ You deploy the Medusa application, with the server and admin, separately from th
You must deploy the Medusa application before the storefront, as it connects to the server and won’t work without a deployed Medusa server URL.
The Medusa application must be deployed to a hosting provider supporting Node.js server deployments, such as Railway, DigitalOcean, AWS, Heroku, etc…
The Medusa application must be deployed to a hosting provider supporting Node.js server deployments.
![Medusa server deployment infrastructure diagram illustrating the backend services ecosystem: the Node.js Medusa server connected to essential services including PostgreSQL database for data storage, and Redis for caching and session management](https://res.cloudinary.com/dza7lstvk/image/upload/v1708600972/Medusa%20Book/backend_deployment_pgexo3.jpg)
Your server connects to a PostgreSQL database, Redis, and other services relevant for your setup. Most hosting providers support deploying and managing these databases along with your Medusa server (such as Railway and DigitalOcean).
Your server connects to a PostgreSQL database, Redis, and other services relevant for your setup. Most hosting providers support deploying and managing these databases along with your Medusa server.
When you deploy your Medusa application, you also deploy the Medusa Admin. For optimal experience, your hosting provider and plan must offer at least 2GB of RAM.