docs: fix start command in deployment guides

medusajs · Feb 24, 2025 · 802cec3 · 802cec3
1 parent 932fd90
commit 802cec3
Show file tree

Hide file tree

Showing 5 changed files with 10,625 additions and 10,629 deletions.
diff --git a/www/apps/book/app/learn/deployment/general/page.mdx b/www/apps/book/app/learn/deployment/general/page.mdx
@@ -218,16 +218,16 @@ Feel free to add any other relevant environment variables, such as for integrati
 
 ### Set Start Command
 
-The Medusa application's production build, which is created using the `build` command, outputs the Medusa application to `.medusa/server`.
-
-So, you must run the `start` command from the `.medusa/server` directory.
+The Medusa application's production build, which is created using the `build` command, outputs the Medusa application to `.medusa/server`. So, you must install the dependencies in the `.medusa/server` directory, then run the `start` command in it.
 
 If your hosting provider doesn't support setting a current-working directory, set the start command to the following:
 
 ```bash npm2yarn
-cd .medusa/server && npm run predeploy && npm run start
+cd .medusa/server && npm install && npm run predeploy && npm run start
 ```
 
+Notice that you run the `predeploy` command before starting the Medusa application to run migrations and sync links whenever there's an update.
+
 ### Set Backend URL in Admin Configuration
 
 After you’ve obtained the Medusa application’s URL, add the following configuration to `medusa-config.ts`:
@@ -293,14 +293,12 @@ Feel free to add any other relevant environment variables, such as for integrati
 
 ### Set Start Command
 
-The Medusa application's production build, which is created using the `build` command, outputs the Medusa application to `.medusa/server`.
-
-So, you must run the `start` command from the `.medusa/server` directory.
+The Medusa application's production build, which is created using the `build` command, outputs the Medusa application to `.medusa/server`. So, you must install the dependencies in the `.medusa/server` directory, then run the `start` command in it.
 
 If your hosting provider doesn't support setting a current-working directory, set the start command to the following:
 
 ```bash npm2yarn
-cd .medusa/server && npm run predeploy && npm run start
+cd .medusa/server && npm run install && npm run start
 ```
 
 ---

diff --git a/www/apps/book/generated/edit-dates.mjs b/www/apps/book/generated/edit-dates.mjs
@@ -104,7 +104,7 @@ export const generatedEditDates = {
   "app/learn/fundamentals/custom-cli-scripts/seed-data/page.mdx": "2024-12-09T14:38:06.385Z",
   "app/learn/fundamentals/environment-variables/page.mdx": "2025-02-18T15:29:37.717Z",
   "app/learn/build/page.mdx": "2024-12-09T11:05:17.383Z",
-  "app/learn/deployment/general/page.mdx": "2024-11-25T14:33:50.439Z",
+  "app/learn/deployment/general/page.mdx": "2025-02-24T07:38:02.164Z",
   "app/learn/fundamentals/workflows/multiple-step-usage/page.mdx": "2024-11-25T16:19:32.169Z",
   "app/learn/installation/page.mdx": "2025-01-31T13:16:57.883Z",
   "app/learn/fundamentals/data-models/check-constraints/page.mdx": "2024-12-06T14:34:50.384Z",