Skip to content

chore(docs): cloud doc changes (automated) #15076

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shahednasser merged 4 commits into from
Apr 10, 2026
+4 −3
Merged

chore(docs): cloud doc changes (automated) #15076

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
87f96c9
chore(docs): automated cloud documentation update
shahednasser Apr 10, 2026
919372a
revert: undo email sender domain entitlement change in emails page
Copilot Apr 10, 2026
88a6228
Apply suggestion from @shahednasser
shahednasser Apr 10, 2026
2aba7ec
revert: undo custom-domains page changes at lines 122-133
Copilot Apr 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion www/apps/cloud/app/emails/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,7 +188,7 @@ Refer to the [Set Up React Email Templates](./react-email/page.mdx) guide to lea

<Note>

Verified email sender domains are available for Launch, Scale, and Enterprise plans only. Learn more about plan features on the [pricing page](../pricing/page.mdx).
Verified email sender domains require the "custom-domain-email" entitlement. Contact support if you need access to this feature.
Copy link
Copy Markdown
Member Author

@shahednasser shahednasser Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot revert this change

Copy link
Copy Markdown
Contributor

Copilot AI Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverted in 919372a.


</Note>

Expand Down
21 changes: 18 additions & 3 deletions www/apps/cloud/app/environments/custom-domains/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,14 @@ To set up a backend custom domain:

You can track your domain's setup progress with the [Domain Status Indicators](#domain-status-indicators).

After setting up your backend custom domain, you'll see a documentation link that provides instructions on how to use the backend domain in your storefront.

<Note>

Once a custom domain is configured, the **Add Domain** button will be hidden to prevent duplicate entries. If you need to change the domain, you must first remove the existing domain.

</Note>

### Update Backend Domain in Storefront

To avoid downtime in you storefront while DNS changes propagate for your backend's custom domain, Medusa doesn't update the backend URL set in the storefront automatically. The storefront will still point to the backend's original subdomain.
Expand Down Expand Up @@ -119,14 +127,21 @@ If no custom domain is configured for your storefront environment, you'll see a
2. Click on the environment card where you want to set up the custom domain.
3. Click the **Settings** tab.
4. Navigate to the **Domains** section.
5. Click the **Add Domain** button.
6. In the modal that opens:
5. If no custom domain is configured, you'll see an informational alert explaining how custom domains provide storefront support.
6. Click the **Add Domain** button.
7. In the modal that opens:
- **Domain Step**: Enter your custom domain name (for example, `shop.acme.com`)
- **DNS Setup**: Follow the instructions to add the required DNS records with your domain provider
7. Click **Done** to complete the setup.
8. Click **Done** to complete the setup.
Copy link
Copy Markdown
Member Author

@shahednasser shahednasser Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot revert this change

Copy link
Copy Markdown
Member Author

@shahednasser shahednasser Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot revert this change

Copy link
Copy Markdown
Contributor

Copilot AI Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverted in 2aba7ec.


You can track your domain's setup progress with the [Domain Status Indicators](#domain-status-indicators).

<Note>

Once a custom domain is configured, the **Add Domain** button will be hidden to prevent duplicate entries. If you need to change the domain, you must first remove the existing domain.

</Note>

---

## Domain Status Indicators
Expand Down
1 change: 1 addition & 0 deletions www/apps/cloud/app/projects/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -201,6 +201,7 @@ On the project's dashboard, you can view the following details:
- Previews environments are created whenever you create a pull request in the linked GitHub repository. They allow you to preview changes before merging them into the main branch.
- Learn more in the [Preview Environments](../environments/preview/page.mdx) guide.
4. **Production URL**: The URL of the project's production deployment. You'll find the backend and storefront URLs (if deployed) under their respective titles in the Production environment card.
- If no backend custom domain is configured for the production environment, you'll see a **Setup Custom Domain** link that allows you to configure a custom domain directly from the environment card.
5. **Repository**: The GitHub repository linked to the project. You'll find it as a "Repository" button at the top right of the project's dashboard. Clicking it will open the repository in a new tab.
6. **Production Deployment Status**: The deployment status of the project for the backend and storefront. If it's "Live", then the deployment was successful. Learn more in the [Deployments](../deployments/page.mdx#deployment-statuses-and-lifecycle) guide.

Expand Down
6 changes: 3 additions & 3 deletions www/apps/cloud/generated/edit-dates.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
export const generatedEditDates = {
"app/page.mdx": "2026-01-08T09:12:42.756Z",
"app/organization/page.mdx": "2025-06-12T14:43:20.772Z",
"app/projects/page.mdx": "2026-04-10T08:04:44.633Z",
"app/projects/page.mdx": "2026-04-10T11:39:54.473Z",
"app/environments/page.mdx": "2026-04-10T10:24:07.265Z",
"app/deployments/page.mdx": "2026-04-10T08:03:45.605Z",
"app/organizations/page.mdx": "2026-04-10T10:23:58.130Z",
Expand All @@ -26,13 +26,13 @@ export const generatedEditDates = {
"app/billing/plans/page.mdx": "2026-04-10T08:03:51.842Z",
"app/cache/page.mdx": "2025-11-12T14:37:24.809Z",
"app/deployments/troubleshooting/page.mdx": "2025-10-17T14:44:22.894Z",
"app/emails/page.mdx": "2026-04-10T08:10:32.105Z",
"app/emails/page.mdx": "2026-04-10T11:40:04.389Z",
"app/emails/react-email/page.mdx": "2026-03-27T09:46:46.277Z",
"app/user/page.mdx": "2025-12-17T12:03:18.968Z",
"app/deployments/access/page.mdx": "2026-04-08T16:20:22.886Z",
"app/projects/prerequisites/page.mdx": "2026-02-09T14:40:20.415Z",
"app/storefront/page.mdx": "2026-04-08T16:19:50.391Z",
"app/projects/rename-repo-branch/page.mdx": "2026-03-18T09:23:58.584Z",
"app/environments/custom-domains/page.mdx": "2026-04-08T16:19:33.834Z",
"app/environments/custom-domains/page.mdx": "2026-04-10T11:39:40.713Z",
"app/command-palette/page.mdx": "2026-04-10T10:20:57.642Z"
}
Loading
⚡