You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: www/apps/cloud/app/database/page.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,10 +43,10 @@ To get the read-only connection string for an environment's database:
43
43
1. From the [organization's dashboard](../organizations/page.mdx), click on the environment's project.
44
44
2. In the project's dashboard, click on the name of the environment. For example, "Production".
45
45
3. In the environment's dashboard, click on the "Settings" tab.
46
-
4. Choose the "Database" tab from the sidebar.
47
-
5.Copy the read-only connection string in the code block.
46
+
4. Choose the "Storage" tab from the sidebar.
47
+
5.In the "Database connection string" section, copy the read-only connection string in the code block.
48
48
49
-
49
+
50
50
51
51
Then, you can connect to your database using a PostgreSQL client. For example, using the `psql` command-line tool:
52
52
@@ -67,7 +67,7 @@ To import or export a database dump for an environment:
67
67
1. From the [organization's dashboard](../organizations/page.mdx), click on the environment's project.
68
68
2. In the project's dashboard, click on the name of the environment. For example, "Production".
69
69
3. In the environment's dashboard, click on the "Settings" tab.
70
-
4. Choose the "Database" tab from the sidebar and find the "Database dump" section.
70
+
4. Choose the "Storage" tab from the sidebar and find the "Database dump" section.
71
71
72
72
Copy file name to clipboardExpand all lines: www/apps/cloud/app/environments/long-lived/page.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -178,9 +178,9 @@ This will change the view to the selected environment, and you'll see its detail
178
178
179
179
---
180
180
181
-
## View Environment Build Logs
181
+
## View Environment Logs
182
182
183
-
You can view runtime logs for an environment in the "Logs" section of the environment's dashboard. These logs help you debug issues in your application.
183
+
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 Medusa application and storefront.
184
184
185
185
Learn more in the [Logs guide](../../logs/page.mdx).
Copy file name to clipboardExpand all lines: www/apps/cloud/app/logs/page.mdx
+14-5Lines changed: 14 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Logs are essential for monitoring your application's health and debugging issues
22
22
There are two types of logs for your environment's deployments:
23
23
24
24
-**Build logs**: Messages generated during the build process before deploying and starting the application. These logs are useful for debugging when a deployment's build fails.
25
-
-**Runtime logs**: Messages logged by the Medusa application when it starts and while it's running, such as informational startup messages, HTTP requests, errors, and more. These logs are useful for debugging the application's deployment and runtime errors.
25
+
-**Runtime logs**: Messages logged by the Medusa backend and storefront when they start and while they're running, such as informational startup messages, HTTP requests, errors, and more. These logs are useful for debugging the application's deployment and runtime errors.
26
26
27
27
---
28
28
@@ -92,12 +92,12 @@ To download build logs, click the <InlineIcon Icon={ArrowDownTray} alt="download
92
92
93
93
## View Runtime Logs on Cloud
94
94
95
-
Runtime logs are useful for debugging the live deployment of an environment's Medusa application, especially when the deployment's status is "Deploy failed". They include logs for:
95
+
Runtime logs are useful for debugging the live deployment of an environment's backend and storefront, especially when the deployment's status is "Deploy failed". They include logs for:
96
96
97
-
- Errors that occur during application startup.
98
-
- Errors that occur when handling incoming HTTP requests, such as 404 errors or 500 server errors.
97
+
- Errors that occur during backend or storefront startup.
98
+
- Errors that occur when handling incoming HTTP requests in the backend, such as 404 errors or 500 server errors.
99
99
- Scheduled jobs, subscribers, and background workflow executions not working as expected (if they log informational or error messages).
100
-
- Other runtime issues that may occur while the application is running.
100
+
- Other runtime issues that may occur while the backend or storefront are running.
101
101
102
102
You can only view the runtime logs of an environment's live deployment, as older deployments are no longer running and do not produce runtime logs.
103
103
@@ -112,6 +112,15 @@ This will open the runtime logs page, where you can see the logs for the live de
112
112
113
113
114
114
115
+
### Switch Between Backend and Storefront Runtime Logs
116
+
117
+
The runtime logs page shows logs for both the Medusa backend and, if you deployed a storefront alongside the Medusa application, the storefront. You can switch between the two using the toggle at the top of the logs table:
118
+
119
+
-**Backend**: Logs from the Medusa backend application, such as HTTP requests, errors, and startup messages.
120
+
-**Storefront**: Logs from the storefront application. This option is only available if you deployed a storefront alongside the Medusa application.
121
+
122
+
123
+
115
124
### Search Runtime Logs
116
125
117
126
You can search the runtime logs using the search bar at the top of the Logs page. This is useful for finding specific messages or errors in the logs.
In this guide, you'll learn how to handle renaming your Cloud project's Git repository or its main branch, and how it affects your Cloud project.
11
+
12
+
## Renaming Repository of a Cloud Project
13
+
14
+
If you rename the Git repository of your Cloud project, Medusa will automatically update the repository URL in your Cloud project settings to reflect the new repository name.
15
+
16
+
However, you need to ensure that your GitHub connection is configured to give Medusa access to the renamed repository. This is necessary for Medusa to continue fetching your code and deploying your environments on Cloud.
17
+
18
+
To reconfigure your GitHub connection after renaming your repository:
19
+
20
+
1. On GitHub, click on your avatar at the top right and choose "Settings" from the dropdown.
21
+
2. In the left sidebar, click on "Applications".
22
+
3. Click on the "Configure" button of the "Medusa" application.
23
+
4. In the "Repository access" section, ensure that either "All repositories" is selected, or if "Only select repositories" is selected, ensure that the renamed repository is included in the list.
24
+
25
+
If your repository is an organization repository, ensure that the GitHub organization also has the renamed repository in its list of repositories that Medusa can access.
26
+
27
+
---
28
+
29
+
## Renaming Branch of a Cloud Project's Repository
30
+
31
+
If you rename the branch associated with an environment of your Cloud project, you need to update the deployment rules of that environment to use the new branch name.
32
+
33
+
To rename the branch associated with an environment of your Cloud project:
34
+
35
+
1. From the [organization's dashboard](../../organizations/page.mdx), click on the environment's project.
36
+
2. In the project's dashboard, click on the name of the environment. For example, "Production".
37
+
3. In the environment's dashboard, click on the "Settings" tab.
38
+
4. Choose the "Deployment rules" tab from the sidebar.
39
+
5. You'll find a `branch` rule. You can edit it by clicking the <InlineIconIcon={EllipsisHorizontal}alt="three-dots" /> icon and choosing "Edit" from the dropdown.
40
+
6. In the side window that opens, you can change the branch that the environment is connected to. For example, you can change it from `main` to `staging` to create a new deployment every time you push a commit to the `staging` branch.
41
+
7. Click "Save" to apply the changes.
42
+
43
+
The deployment rules will take effect for next deployments. So, the next time you push a commit to the renamed branch, it will trigger a new deployment of the environment.
Copy file name to clipboardExpand all lines: www/apps/cloud/app/s3/page.mdx
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,24 @@ If you're using a Medusa version before v2.7.0, contact support for assistance i
30
30
31
31
### Access S3 Configurations on Cloud
32
32
33
-
Since Cloud is a managed service, you can't directly access your S3 bucket or its configurations. Medusa also doesn't expose the S3 bucket connection or configuration details.
33
+
Since Cloud is a managed service, you can't directly access your S3 bucket.
34
+
35
+
You can, however, access the S3 bucket details of your environment. This is useful when setting remote patterns in your storefront to allow loading assets from the S3 bucket.
36
+
37
+
To access the S3 bucket details of an environment:
38
+
39
+
1. From the [organization's dashboard](../organizations/page.mdx), click on the environment's project.
40
+
2. In the project's dashboard, click on the name of the environment. For example, "Production".
41
+
3. In the environment's dashboard, click on the "Settings" tab.
42
+
4. Choose the "Storage" tab from the sidebar.
43
+
5. In the "Object storage" section, you can find your full S3 file URL and your S3 endpoint.
44
+
45
+
From the S3 file URL, you can extract the bucket name and region. For example, if your S3 file URL is `https://s3.eu-central-1.amazonaws.com/medusajs.cloud-data-prod-euc1-123`:
46
+
47
+
- The bucket name is `medusajs.cloud-data-prod-euc1-123`.
48
+
- The region is `eu-central-1`.
49
+
50
+
0 commit comments