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

docs: improve headings and context in Cloud docs (#13757)

Browse Source
This commit is contained in:
Shahed Nasser
2025-10-15 18:49:48 +03:00
committed by GitHub
parent 4e3090ab26
commit 8bb036457c
13 changed files with 68 additions and 68 deletions
Download Patch File Download Diff File Expand all files Collapse all files
www/apps/cloud/app/environments/environment-variables/page.mdx
+4 -4
View File
@@ -41,7 +41,7 @@ The following environment variable names are reserved by Cloud and you can't use
---
## Add Environment Variables
## Add Environment Variables on Cloud
To add environment variables to an environment:
@@ -67,7 +67,7 @@ After adding the environment variables, you must [redeploy the environment](../l
---
## Edit Environment Variables
## Edit Environment Variables on Cloud
To edit an environment variable:
@@ -92,7 +92,7 @@ After editing the environment variable, you must [redeploy the environment](../l
---
## Delete Environment Variables
## Delete Environment Variables on Cloud
To delete an environment variable:
@@ -112,7 +112,7 @@ After deleting the environment variable, you must [redeploy the environment](../
---
## Export Environment Variables
## Export Environment Variables on Cloud
You can export an environment's variables as a `.env` file. This is useful for debugging issues that require you to have the same environment variables.
www/apps/cloud/app/environments/long-lived/page.mdx
+1 -1
View File
@@ -27,7 +27,7 @@ Production and long-lived environments are stable and scalable, making them idea
---
## Create a Long-Lived Environment
## Create a Long-Lived Environment on Cloud
It's recommended to create long-lived environments for different stages of your project's development.
www/apps/cloud/app/environments/page.mdx
+3 -3
View File
@@ -4,11 +4,11 @@ export const metadata = {
# {metadata.title}
In this guide, you'll learn about environments, how to create and manage them, and how to use preview environments.
In this guide, you'll learn about environments in Cloud, how to create and manage them, and how to use preview environments.
## Environments Overview
A project can have multiple environments, each representing a different stage of your application. For example, you can have a Production environment for your live application, and a Staging environment for testing new features.
A Cloud project can have multiple environments, each representing a different stage of your application. For example, you can have a Production environment for your live application, and a Staging environment for testing new features.
Each environment has its own resources, such as a database and server instance. By default, a project has at least a Production environment, and you can create custom environments based on your development needs.
@@ -23,7 +23,7 @@ There are two types of environments:
---
## View Project's Environments
## View Project's Environments on Cloud
To view a project's environments:
www/apps/cloud/app/environments/preview/page.mdx
+1 -1
View File
@@ -4,7 +4,7 @@ export const metadata = {
# {metadata.title}
A preview environment is a short-lived environment that is automatically created for each pull request (PR) opened towards a branch with a long-lived environment in Cloud.
A preview environment is a short-lived Cloud environment that is automatically created for each pull request (PR) opened towards a branch with a long-lived environment in Cloud.
Preview environments facilitate testing a PR's changes in a live environment before merging them. They allow you to test changes in an environment that closely resembles the target long-lived environment.