docs: updates for storefront in cloud (#14491)
* docs: updates for storefront in cloud * comment-out pnpm * fix broken link * npm prerequisites * Update www/apps/cloud/app/storefront/page.mdx Co-authored-by: Stevche Radevski <sradevski@live.com> * remove global cdn --------- Co-authored-by: Stevche Radevski <sradevski@live.com>
This commit is contained in:
Shahed Nasser
co-authored by
Stevche Radevski
Stevche Radevski
parent
bb599a26de
commit
baaee11114
@@ -37,37 +37,42 @@ To view the build logs for a deployment:
|
||||
1. Make sure you're viewing the [correct organization's dashboard in Cloud](../organizations/page.mdx#switch-organization).
|
||||
2. Click on the project that the deployment belongs to.
|
||||
3. Click on the environment that the deployment belongs to, such as "Production".
|
||||
4. Under the "Deployments" section, find the deployment you want to view the build logs for and click on it.
|
||||
4. In the "Deployments" table, find the deployment you want to view the build logs for and click on it.
|
||||
|
||||
This will open the deployment details page, where you can see the build logs. The build logs are updated in real time as the build process runs, so you can see the progress and any errors that occur during the build.
|
||||
This will open the deployment details page, where you can see the deployment's activity:
|
||||
|
||||
|
||||
- **Backend build logs**: Logs for building the Medusa backend.
|
||||
- **Storefront build logs**: If you deployed a storefront alongside the Medusa application, this shows the logs for building the storefront.
|
||||
|
||||
The build logs are updated in real time as the build process runs, so you can see the progress and any errors that occur during the build.
|
||||
|
||||
|
||||
|
||||
### Search Build Logs on Cloud
|
||||
|
||||
You can search the build logs using the search bar at the top right of the "Build logs" section. This is useful for finding specific messages or errors in the logs.
|
||||
You can search the build logs (for backend and storefront) using the search bar at the top right of the logs. This is useful for finding specific messages or errors in the logs.
|
||||
|
||||
For example, you can search for keywords like "error" or "warning" to quickly locate issues in the build process.
|
||||
|
||||
When you enter the search term, you'll see how many results match your search. You can then move between the results using the up and down arrows next to the search bar. The matching text will be highlighted in the logs.
|
||||
When you enter the search term, you'll see how the results matching your search. You can move between the results using the up and down arrows next to the search bar. The matching text will be highlighted in the logs.
|
||||
|
||||
|
||||
|
||||
|
||||
### Expand and Collapse Build Logs on Cloud
|
||||
|
||||
Logs for steps in the build process can be expanded or collapsed to improve readability. This is useful when you have many log messages and want to focus on specific parts of the build process.
|
||||
|
||||
By default, logs for all steps in the build process are expanded. You can collapse all logs by clicking the "Collapse all" button at the top right of the "Build logs" section. This will hide all the detailed logs and only show the titles of each step.
|
||||
By default, logs for all steps in the build process are expanded. You can collapse all logs by clicking the "Collapse all" button at the top right of the logs. This will hide all the detailed logs and only show the titles of each step.
|
||||
|
||||
|
||||
|
||||
|
||||
You can also expand the logs of all steps in the build process by clicking the "Expand all" button at the top right. This will show all the detailed logs for each step.
|
||||
|
||||
|
||||
|
||||
|
||||
In addition, you can expand or collapse individual steps by clicking the arrow next to a step's title. This gives you more control over which parts of the logs you want to see or hide.
|
||||
|
||||
|
||||
|
||||
|
||||
### Pause Build Logs on Cloud
|
||||
|
||||
@@ -75,21 +80,19 @@ When you view the build logs while the build is still in progress, you can pause
|
||||
|
||||
To pause the build logs, click the "Pause" button at the bottom right of the page. This button is only shown when there are incoming log messages. When you pause the logs, the button will change to "Resume", allowing you to resume the live log updates.
|
||||
|
||||
|
||||
|
||||
### Download Build Logs on Cloud
|
||||
|
||||
You can download the build logs as a `.log` file for offline analysis, sharing with your team, or sharing with Cloud support if you need help debugging a build issue.
|
||||
|
||||
To download build logs, click the <InlineIcon Icon={ArrowDownTray} alt="download" /> button at the top right of the "Build logs" section. This will download the logs in a `.log` file format, which you can open with any text editor.
|
||||
To download build logs, click the <InlineIcon Icon={ArrowDownTray} alt="download" /> button at the top right of the logs. This will download the logs in a `.log` file format, which you can open with any text editor.
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
## View Runtime Logs on Cloud
|
||||
|
||||
Runtime logs are useful for debugging the live deployment of an environment, especially when the deployment's status is "Deploy failed". They include logs for:
|
||||
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:
|
||||
|
||||
- Errors that occur during application startup.
|
||||
- Errors that occur when handling incoming HTTP requests, such as 404 errors or 500 server errors.
|
||||
|
||||
Reference in New Issue
Block a user