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

docs: wording and structural changes to cloud (#12820)

Browse Source 
* docs: wording and structural changes to cloud

* Fix vale error

* Fix faq title

* Fix heading levels

* Small change to previews
This commit is contained in:
Shahed Nasser
2025-06-25 12:20:02 +03:00
committed by GitHub
parent 820a936b98
commit 91f6cfad5d
24 changed files with 713 additions and 663 deletions
Download Patch File Download Diff File Expand all files Collapse all files
www/apps/cloud/app/update-medusa/page.mdx
+5 -5
View File
@@ -30,7 +30,7 @@ It's **strongly discouraged** to push a new update directly to your production b
By using a separate environment, you mitigate any unexpected issues that may arise during the update process. This way, you ensure that your customizations and configurations work correctly with the new version of Medusa.
The **recommended** approach is to [create a long-lived environment](../environments/page.mdx#create-a-long-lived-environment), such as Staging. You can push the new update and test it thoroughly in a production-like environment before deploying it to production.
The **recommended** approach is to [create a long-lived environment](../environments/long-lived/page.mdx#create-a-long-lived-environment), such as Staging. You can push the new update and test it thoroughly in a production-like environment before deploying it to production.
<Note title="Tip">
@@ -40,7 +40,7 @@ Each environment has its own database, so you can safely update other environmen
![Diagram showcasing process of deploying to staging then production](https://res.cloudinary.com/dza7lstvk/image/upload/v1750334010/Cloud/deploy-to-staging_d4oyys.jpg)
Alternatively, you can open a pull request to the production branch, which will [create a preview environment](../environments/page.mdx#preview-environments). The preview environment allows you to test the update before merging it into the production branch.
Alternatively, you can open a pull request to the production branch, which will [create a preview environment](../environments/preview/page.mdx#preview-environments). The preview environment allows you to test the update before merging it into the production branch.
![Diagram showcasing process of deploying to preview then production](https://res.cloudinary.com/dza7lstvk/image/upload/v1750334010/Cloud/deploy-to-preview_plpz9z.jpg)
@@ -59,7 +59,7 @@ To update your Medusa application deployed on Cloud:
1. Update your Medusa application locally either on the long-lived environment's branch (for example, Staging) or in a new branch that will be used to create a pull request.
- To learn how to update your Medusa application, refer to the [Update guide](!docs!/learn/update). It includes all the details you need to update the Medusa application locally.
2. Once you're done updating your application locally, push the changes in `package.json`, lock file (for example, `yarn.lock`), and any other affected files to the branch.
- If you're using a long-lived environment, Cloud will automatically deploy the changes to the branch's environment.
- If you're using a long-lived environment, Medusa will automatically deploy the changes to the branch's environment.
- If you're using a new branch to create a pull request, open the pull request to the production branch. This will create a preview environment that you can use to test the update before merging it into the production branch.
Then, you can access the environment's [live deployment](../deployments/page.mdx#access-live-deployment) to test the update. You can also use the [build](../logs/page.mdx#view-build-logs) and [runtime](../logs/page.mdx#view-runtime-logs) logs of the environment to debug any issues that occur during the update process or testing.
@@ -68,7 +68,7 @@ Then, you can access the environment's [live deployment](../deployments/page.mdx
Once you've thoroughly tested the update in your long-lived or preview environment, you can merge the changes into your production branch.
Cloud will automatically deploy the changes to the production environment. This will update the production's code and database.
Medusa will automatically deploy the changes to the production environment. This will update the production's code and database.
---
@@ -76,4 +76,4 @@ Cloud will automatically deploy the changes to the production environment. This
If you encounter any issues after updating your deployed Medusa application, you can [redeploy a previous deployment](../deployments/page.mdx#redeploy-a-deployment) to roll back the code changes made by the update.
However, redeploying a previous deployment will not roll back the database changes made by the update. If you need to roll back the database changes, [contact support](../support/page.mdx) for assistance.
However, redeploying a previous deployment will not roll back the database changes made by the update. If you need to roll back the database changes, contact support for assistance.