From e7abfc8ca183b4353baa6e2b0eaff17f833eae16 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 15 May 2026 23:52:37 +0000 Subject: [PATCH] docs: update Mintlify deployment domain from mintlify.dev to mintlify.cc --- deploy/authentication-setup.mdx | 2 +- deploy/cloudflare.mdx | 4 +- deploy/csp-configuration.mdx | 12 +++--- deploy/reverse-proxy.mdx | 60 +++++++++++++++--------------- deploy/route53-cloudfront.mdx | 12 +++--- deploy/vercel.mdx | 6 +-- es/deploy/authentication-setup.mdx | 2 +- es/deploy/cloudflare.mdx | 4 +- es/deploy/csp-configuration.mdx | 12 +++--- es/deploy/reverse-proxy.mdx | 60 +++++++++++++++--------------- es/deploy/route53-cloudfront.mdx | 12 +++--- es/deploy/vercel.mdx | 6 +-- fr/deploy/authentication-setup.mdx | 2 +- fr/deploy/cloudflare.mdx | 4 +- fr/deploy/csp-configuration.mdx | 12 +++--- fr/deploy/reverse-proxy.mdx | 60 +++++++++++++++--------------- fr/deploy/route53-cloudfront.mdx | 12 +++--- fr/deploy/vercel.mdx | 6 +-- zh/deploy/authentication-setup.mdx | 2 +- zh/deploy/cloudflare.mdx | 4 +- zh/deploy/csp-configuration.mdx | 12 +++--- zh/deploy/reverse-proxy.mdx | 60 +++++++++++++++--------------- zh/deploy/route53-cloudfront.mdx | 12 +++--- zh/deploy/vercel.mdx | 6 +-- 24 files changed, 192 insertions(+), 192 deletions(-) diff --git a/deploy/authentication-setup.mdx b/deploy/authentication-setup.mdx index fe9b86142a..ea51bb6930 100644 --- a/deploy/authentication-setup.mdx +++ b/deploy/authentication-setup.mdx @@ -11,7 +11,7 @@ keywords: ['authentication', 'auth', 'OAuth', 'JWT', 'password'] - Authentication is only available for documentation hosted on a custom domain or Mintlify subdomain (for example, `docs.example.com` or `example.mintlify.dev`). Authentication is **not supported** when using a [custom basepath](/deploy/docs-subpath) (for example, `example.com/docs`). + Authentication is only available for documentation hosted on a custom domain or Mintlify subdomain (for example, `docs.example.com` or `example.mintlify.cc`). Authentication is **not supported** when using a [custom basepath](/deploy/docs-subpath) (for example, `example.com/docs`). Authentication requires users to log in before accessing your documentation. diff --git a/deploy/cloudflare.mdx b/deploy/cloudflare.mdx index e20c403651..25673cfd07 100644 --- a/deploy/cloudflare.mdx +++ b/deploy/cloudflare.mdx @@ -65,7 +65,7 @@ async function handleRequest(request) { // If the request is to the docs subpath if (/^\/docs/.test(urlObject.pathname)) { // Then Proxy to Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.cc"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); @@ -148,7 +148,7 @@ If you use Webflow to host your main site and want to serve Mintlify docs at `/d // If the request is to the docs subpath if (/^\/docs/.test(urlObject.pathname)) { // Proxy to Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.cc"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); url.hostname = DOCS_URL; diff --git a/deploy/csp-configuration.mdx b/deploy/csp-configuration.mdx index 0ee0f384b3..29b7324c13 100644 --- a/deploy/csp-configuration.mdx +++ b/deploy/csp-configuration.mdx @@ -24,7 +24,7 @@ The following CSP directives control which resources a page can load: | Domain | Purpose | CSP directive | Required | |:-------|:--------|:--------------|:-------| | `d4tuoctqmanu0.cloudfront.net` | KaTeX CSS, fonts | `style-src`, `font-src` | Required | -| `*.mintlify.dev` | Documentation content | `connect-src`, `frame-src` | Required | +| `*.mintlify.cc` | Documentation content | `connect-src`, `frame-src` | Required | | `*.mintlify.com` | Dashboard, API, analytics proxy | `connect-src` | Required | | `leaves.mintlify.com` | Assistant API | `connect-src` | Required | | `d3gk2c5xim1je2.cloudfront.net` | Icons, images, logos | `img-src` | Required | @@ -62,9 +62,9 @@ browser.sentry-cdn.com js.sentry-cdn.com hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; -connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com +connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com www.googletagmanager.com cdn.segment.com plausible.io us.posthog.com browser.sentry-cdn.com hcaptcha.com *.hcaptcha.com; -frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; +frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com; ``` ## Common configurations by proxy type @@ -82,7 +82,7 @@ Create a Response Header Transform Rule: - **Header name**: `Content-Security-Policy` - **Header value**: ```text wrap - default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; + default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com; ``` 4. Deploy your rule. @@ -97,7 +97,7 @@ Add a response headers policy in CloudFront: "Config": { "SecurityHeadersConfig": { "ContentSecurityPolicy": { - "ContentSecurityPolicy": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com;", + "ContentSecurityPolicy": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com;", "Override": true } } @@ -118,7 +118,7 @@ Add to your `vercel.json`: "headers": [ { "key": "Content-Security-Policy", - "value": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com;" + "value": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com;" } ] } diff --git a/deploy/reverse-proxy.mdx b/deploy/reverse-proxy.mdx index 2c3342d814..076845305c 100644 --- a/deploy/reverse-proxy.mdx +++ b/deploy/reverse-proxy.mdx @@ -12,7 +12,7 @@ When you implement a reverse proxy, monitor for potential issues with domain ver Mintlify supports two reverse proxy configurations depending on your subpath requirements. -- **Host at `/docs`**: Use `mintlify.dev` as the proxy target. Enable the **Host at `/docs`** toggle on the [Custom domain setup](https://dashboard.mintlify.com/settings/deployment/custom-domain) page in your dashboard. This is a simpler configuration with fewer routes. +- **Host at `/docs`**: Use `mintlify.cc` as the proxy target. Enable the **Host at `/docs`** toggle on the [Custom domain setup](https://dashboard.mintlify.com/settings/deployment/custom-domain) page in your dashboard. This is a simpler configuration with fewer routes. - **Custom subpath**: Use `mintlify.app` as the proxy target. This approach supports any subpath and requires additional routing rules. ## Host at `/docs` subpath @@ -26,7 +26,7 @@ Before configuring your reverse proxy: 3. Enter your domain and click **Add domain**. - When you enable **Host at `/docs`**, your canonical docs URL becomes `.mintlify.dev`. Cache invalidation stops on `mintlify.app`, and you must proxy to `mintlify.dev` for updates to appear. + When you enable **Host at `/docs`**, your canonical docs URL becomes `.mintlify.cc`. Cache invalidation stops on `mintlify.app`, and you must proxy to `mintlify.cc` for updates to appear. ### Routing configuration @@ -35,14 +35,14 @@ Proxy these paths to your Mintlify subdomain: | Path | Destination | Caching | | --------------------------------- | ------------------------------------ | -------- | -| `/docs` | `.mintlify.dev/docs` | No cache | -| `/docs/*` | `.mintlify.dev/docs` | No cache | -| `/.well-known/vercel/*` | `.mintlify.dev` | No cache | -| `/.well-known/skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/.well-known/agent-skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/skill.md` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms.txt` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms-full.txt` (optional) | `.mintlify.dev/docs` | No cache | +| `/docs` | `.mintlify.cc/docs` | No cache | +| `/docs/*` | `.mintlify.cc/docs` | No cache | +| `/.well-known/vercel/*` | `.mintlify.cc` | No cache | +| `/.well-known/skills/*` (optional) | `.mintlify.cc/docs` | No cache | +| `/.well-known/agent-skills/*` (optional) | `.mintlify.cc/docs` | No cache | +| `/skill.md` (optional) | `.mintlify.cc/docs` | No cache | +| `/llms.txt` (optional) | `.mintlify.cc/docs` | No cache | +| `/llms-full.txt` (optional) | `.mintlify.cc/docs` | No cache | The `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, `/llms.txt`, and `/llms-full.txt` routes are optional. Include them only if you want to serve AI files at root paths like `your-domain.com/llms.txt` instead of under your docs subpath like `your-domain.com/docs/llms.txt`. @@ -50,7 +50,7 @@ The `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, `/llms. Configure your reverse proxy with these header requirements: -- **Origin**: Contains the target subdomain `.mintlify.dev` +- **Origin**: Contains the target subdomain `.mintlify.cc` - **X-Forwarded-For**: Preserves client IP information - **X-Forwarded-Proto**: Preserves original protocol (HTTP/HTTPS) - **X-Real-IP**: Forwards the real client IP address @@ -69,8 +69,8 @@ server { # Vercel verification paths location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.dev; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -81,8 +81,8 @@ server { # AI skills paths location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -93,8 +93,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -105,8 +105,8 @@ server { # Skill manifest (optional) location = /skill.md { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -117,8 +117,8 @@ server { # LLM index files (optional) location = /llms.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -128,8 +128,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -140,8 +140,8 @@ server { # Documentation root location = /docs { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -152,8 +152,8 @@ server { # All documentation paths location /docs/ { - proxy_pass https://.mintlify.dev/docs/; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs/; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -381,9 +381,9 @@ server { **Symptoms**: You publish documentation updates, but the changes don't appear on your site. -**Cause**: You have **Host at `/docs`** enabled in your dashboard but your reverse proxy points to `mintlify.app` instead of `mintlify.dev`. +**Cause**: You have **Host at `/docs`** enabled in your dashboard but your reverse proxy points to `mintlify.app` instead of `mintlify.cc`. -**Solution**: Update your reverse proxy configuration to point to `.mintlify.dev` instead of `.mintlify.app`. +**Solution**: Update your reverse proxy configuration to point to `.mintlify.cc` instead of `.mintlify.app`. ### 404 error @@ -394,7 +394,7 @@ server { **Solution**: - Remove `Host` header forwarding -- Set `Origin` header to your Mintlify subdomain (`mintlify.dev` for a `/docs` subpath or `mintlify.app` for a different subpath) +- Set `Origin` header to your Mintlify subdomain (`mintlify.cc` for a `/docs` subpath or `mintlify.app` for a different subpath) ### Performance issues diff --git a/deploy/route53-cloudfront.mdx b/deploy/route53-cloudfront.mdx index d63db1249d..cf3abbcae6 100644 --- a/deploy/route53-cloudfront.mdx +++ b/deploy/route53-cloudfront.mdx @@ -36,10 +36,10 @@ All Behaviors must have an **origin request policy** of `AllViewerExceptHostHead ![CloudFront Distributions page with the "Create distribution" button emphasized.](/images/cloudfront/create-distribution.png) -3. For the Origin domain, input `[SUBDOMAIN].mintlify.dev` where `[SUBDOMAIN]` is your project's unique subdomain. +3. For the Origin domain, input `[SUBDOMAIN].mintlify.cc` where `[SUBDOMAIN]` is your project's unique subdomain. - ![CloudFront "Create distribution" page showing "acme.mintlify.dev" as the origin domain.](/images/cloudfront/origin-name.png) + ![CloudFront "Create distribution" page showing "acme.mintlify.cc" as the origin domain.](/images/cloudfront/origin-name.png) 4. For "Web Application Firewall (WAF)," enable security protections. @@ -83,7 +83,7 @@ By this point, you should have two Origins: one with `[SUBDOMAIN].mintlify.app` Behaviors in CloudFront enable control over the subpath logic. At a high level, we're looking to create the following logic: -- **If a user lands on your custom subpath**, go to `[SUBDOMAIN].mintlify.dev`. +- **If a user lands on your custom subpath**, go to `[SUBDOMAIN].mintlify.cc`. - **If a user lands on any other page**, go to the current landing page. 1. Navigate to the "Behaviors" tab of your CloudFront distribution. @@ -112,19 +112,19 @@ If `.well-known/*` is too generic, it can be narrowed down to 2 behaviors at a m ### Your subpath -Create a behavior with a **Path pattern** of your chosen subpath, for example `/docs`, with **Origin and origin groups** pointing to the `.mintlify.dev` URL (in our case `acme.mintlify.dev`). +Create a behavior with a **Path pattern** of your chosen subpath, for example `/docs`, with **Origin and origin groups** pointing to the `.mintlify.cc` URL (in our case `acme.mintlify.cc`). - Set "Cache policy" to **CachingOptimized**. - Set "Origin request policy" to **AllViewerExceptHostHeader**. - Set Viewer Protocol Policy to **Redirect HTTP to HTTPS** - ![CloudFront "Create behavior" page with a "Path pattern" of "/docs/*" and "Origin and origin groups" pointing to the `acme.mintlify.dev` URL.](/images/cloudfront/behavior-1.png) + ![CloudFront "Create behavior" page with a "Path pattern" of "/docs/*" and "Origin and origin groups" pointing to the `acme.mintlify.cc` URL.](/images/cloudfront/behavior-1.png) ### Your subpath with wildcard -Create a behavior with a **Path pattern** of your chosen subpath followed by `/*`, for example `/docs/*`, and **Origin and origin groups** pointing to the same `.mintlify.dev` URL. +Create a behavior with a **Path pattern** of your chosen subpath followed by `/*`, for example `/docs/*`, and **Origin and origin groups** pointing to the same `.mintlify.cc` URL. These settings should exactly match your base subpath behavior. With the exception of the **Path pattern**. diff --git a/deploy/vercel.mdx b/deploy/vercel.mdx index f0d4ea200e..0496981d33 100644 --- a/deploy/vercel.mdx +++ b/deploy/vercel.mdx @@ -15,7 +15,7 @@ The `vercel.json` file configures how your project builds and deploys. It sits i We use the `rewrites` configuration in your `vercel.json` file to proxy requests from your main domain to your documentation. -Rewrites map incoming requests to different destinations without changing the URL in the browser. When someone visits `yoursite.com/docs`, Vercel internally fetches content from `your-subdomain.mintlify.dev/docs`, but the user still sees `yoursite.com/docs` in their browser. This is different from redirects, which send users to another URL entirely. +Rewrites map incoming requests to different destinations without changing the URL in the browser. When someone visits `yoursite.com/docs`, Vercel internally fetches content from `your-subdomain.mintlify.cc/docs`, but the user still sees `yoursite.com/docs` in their browser. This is different from redirects, which send users to another URL entirely. ## Configuration @@ -36,11 +36,11 @@ Rewrites map incoming requests to different destinations without changing the UR "rewrites": [ { "source": "/docs", - "destination": "https://[subdomain].mintlify.dev/docs" + "destination": "https://[subdomain].mintlify.cc/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlify.dev/docs/:match*" + "destination": "https://[subdomain].mintlify.cc/docs/:match*" } ] } diff --git a/es/deploy/authentication-setup.mdx b/es/deploy/authentication-setup.mdx index 8a7799fef1..c19a17d30d 100644 --- a/es/deploy/authentication-setup.mdx +++ b/es/deploy/authentication-setup.mdx @@ -11,7 +11,7 @@ keywords: ['authentication', 'auth', 'OAuth', 'JWT', 'password'] - La autenticación solo está disponible para documentación alojada en un dominio personalizado o subdominio de Mintlify (por ejemplo, `docs.ejemplo.com` o `ejemplo.mintlify.dev`). La autenticación **no es compatible** cuando se usa una [ruta base personalizada](/es/deploy/docs-subpath) (por ejemplo, `ejemplo.com/docs`). + La autenticación solo está disponible para documentación alojada en un dominio personalizado o subdominio de Mintlify (por ejemplo, `docs.ejemplo.com` o `ejemplo.mintlify.cc`). La autenticación **no es compatible** cuando se usa una [ruta base personalizada](/es/deploy/docs-subpath) (por ejemplo, `ejemplo.com/docs`). La autenticación exige que los usuarios inicien sesión antes de acceder a tu documentación. diff --git a/es/deploy/cloudflare.mdx b/es/deploy/cloudflare.mdx index 715981def1..faec0cbdce 100644 --- a/es/deploy/cloudflare.mdx +++ b/es/deploy/cloudflare.mdx @@ -76,7 +76,7 @@ async function handleRequest(request) { // Si la solicitud es al subpath de docs if (/^\/docs/.test(urlObject.pathname)) { // Entonces hacer proxy a Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.cc"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); @@ -169,7 +169,7 @@ Si usas Webflow para alojar tu sitio principal y quieres servir la documentació // Si la solicitud es al subdirectorio de documentación if (/^\/docs/.test(urlObject.pathname)) { // Proxy a Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.cc"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); url.hostname = DOCS_URL; diff --git a/es/deploy/csp-configuration.mdx b/es/deploy/csp-configuration.mdx index f6b2373d25..287126ca49 100644 --- a/es/deploy/csp-configuration.mdx +++ b/es/deploy/csp-configuration.mdx @@ -28,7 +28,7 @@ Las siguientes directivas de CSP controlan qué recursos puede cargar una págin | Dominio | Propósito | Directiva CSP | Obligatorio | |:-------|:--------|:--------------|:-------| | `d4tuoctqmanu0.cloudfront.net` | CSS y fuentes de KaTeX | `style-src`, `font-src` | Obligatorio | -| `*.mintlify.dev` | Contenido de la documentación | `connect-src`, `frame-src` | Obligatorio | +| `*.mintlify.cc` | Contenido de la documentación | `connect-src`, `frame-src` | Obligatorio | | `*.mintlify.com` | Dashboard, API, proxy de Analytics | `connect-src` | Obligatorio | | `leaves.mintlify.com` | API del assistant | `connect-src` | Obligatorio | | `d3gk2c5xim1je2.cloudfront.net` | Íconos, imágenes, logotipos | `img-src` | Obligatorio | @@ -68,9 +68,9 @@ browser.sentry-cdn.com js.sentry-cdn.com hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; -connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com +connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com www.googletagmanager.com cdn.segment.com plausible.io us.posthog.com browser.sentry-cdn.com hcaptcha.com *.hcaptcha.com; -frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; +frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com; ``` @@ -94,7 +94,7 @@ Crea una regla de transformación de encabezados de respuesta: - **Header name**: `Content-Security-Policy` - **Header value**: ```text wrap - default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; + default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com; ``` 4. Publica la regla. @@ -112,7 +112,7 @@ Agrega una política de encabezados de respuesta en CloudFront: "Config": { "SecurityHeadersConfig": { "ContentSecurityPolicy": { - "ContentSecurityPolicy": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com;", + "ContentSecurityPolicy": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com;", "Override": true } } @@ -136,7 +136,7 @@ Agrega en tu `vercel.json`: "headers": [ { "key": "Content-Security-Policy", - "value": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com;" + "value": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com;" } ] } diff --git a/es/deploy/reverse-proxy.mdx b/es/deploy/reverse-proxy.mdx index e39adab9ee..b139a30577 100644 --- a/es/deploy/reverse-proxy.mdx +++ b/es/deploy/reverse-proxy.mdx @@ -14,7 +14,7 @@ Al implementar un proxy inverso, supervisa posibles problemas con la verificaci Mintlify admite dos configuraciones de proxy inverso en función de tus requisitos de subruta. -- **Alojar en `/docs`**: Usa `mintlify.dev` como destino del proxy. Activa la opción **Host at `/docs`** en la página [Custom domain setup](https://dashboard.mintlify.com/settings/deployment/custom-domain) de tu dashboard. Esta es una configuración más sencilla con menos rutas. +- **Alojar en `/docs`**: Usa `mintlify.cc` como destino del proxy. Activa la opción **Host at `/docs`** en la página [Custom domain setup](https://dashboard.mintlify.com/settings/deployment/custom-domain) de tu dashboard. Esta es una configuración más sencilla con menos rutas. - **Subruta personalizada**: Usa `mintlify.app` como destino del proxy. Este enfoque admite cualquier subruta y requiere reglas de enrutamiento adicionales.
@@ -30,7 +30,7 @@ Antes de configurar tu proxy inverso: 3. Ingresa tu domain y selecciona **Add domain**. - Cuando activas **Host at `/docs`**, la URL canónica de tu documentación se convierte en `.mintlify.dev`. La invalidación de caché se detiene en `mintlify.app` y debes dirigir el proxy a `mintlify.dev` para que aparezcan las actualizaciones. + Cuando activas **Host at `/docs`**, la URL canónica de tu documentación se convierte en `.mintlify.cc`. La invalidación de caché se detiene en `mintlify.app` y debes dirigir el proxy a `mintlify.cc` para que aparezcan las actualizaciones.
@@ -41,14 +41,14 @@ Encamina (proxy) estas rutas a tu subdomain de Mintlify: | Ruta | Destino | Caché | | --------------------------------- | ----------------------------------- | -------- | -| `/docs` | `.mintlify.dev/docs` | Sin caché | -| `/docs/*` | `.mintlify.dev/docs` | Sin caché | -| `/.well-known/vercel/*` | `.mintlify.dev` | Sin caché | -| `/.well-known/skills/*` (opcional) | `.mintlify.dev/docs` | Sin caché | -| `/.well-known/agent-skills/*` (opcional) | `.mintlify.dev/docs` | Sin caché | -| `/skill.md` (opcional) | `.mintlify.dev/docs` | Sin caché | -| `/llms.txt` (opcional) | `.mintlify.dev/docs` | Sin caché | -| `/llms-full.txt` (opcional) | `.mintlify.dev/docs` | Sin caché | +| `/docs` | `.mintlify.cc/docs` | Sin caché | +| `/docs/*` | `.mintlify.cc/docs` | Sin caché | +| `/.well-known/vercel/*` | `.mintlify.cc` | Sin caché | +| `/.well-known/skills/*` (opcional) | `.mintlify.cc/docs` | Sin caché | +| `/.well-known/agent-skills/*` (opcional) | `.mintlify.cc/docs` | Sin caché | +| `/skill.md` (opcional) | `.mintlify.cc/docs` | Sin caché | +| `/llms.txt` (opcional) | `.mintlify.cc/docs` | Sin caché | +| `/llms-full.txt` (opcional) | `.mintlify.cc/docs` | Sin caché | Las rutas `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, `/llms.txt` y `/llms-full.txt` son opcionales. Inclúyelas solo si quieres servir archivos de IA en rutas raíz como `your-domain.com/llms.txt` en lugar de en tu subruta de documentación, como `your-domain.com/docs/llms.txt`. @@ -56,7 +56,7 @@ Las rutas `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, ` Configura tu proxy inverso con estos requisitos de encabezados: -* **Origin**: Contiene el subdomain de destino `.mintlify.dev` +* **Origin**: Contiene el subdomain de destino `.mintlify.cc` * **X-Forwarded-For**: Conserva la información de la IP del cliente * **X-Forwarded-Proto**: Conserva el protocolo original (HTTP/HTTPS) * **X-Real-IP**: Reenvía la dirección IP real del cliente @@ -77,8 +77,8 @@ server { # Rutas de verificación de Vercel location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.dev; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -89,8 +89,8 @@ server { # Rutas de habilidades de IA location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -101,8 +101,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -113,8 +113,8 @@ server { # Manifiesto de habilidad (opcional) location = /skill.md { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -125,8 +125,8 @@ server { # Archivos de índice LLM (opcional) location = /llms.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -136,8 +136,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -148,8 +148,8 @@ server { # Raíz de la documentación location = /docs { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -160,8 +160,8 @@ server { # Todas las rutas de la documentación location /docs/ { - proxy_pass https://.mintlify.dev/docs/; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs/; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -401,9 +401,9 @@ server { **Síntomas**: Publicas actualizaciones de la documentación, pero los cambios no aparecen en tu sitio. -**Causa**: Tienes **Host at `/docs`** activado en tu dashboard, pero tu proxy inverso apunta a `mintlify.app` en lugar de `mintlify.dev`. +**Causa**: Tienes **Host at `/docs`** activado en tu dashboard, pero tu proxy inverso apunta a `mintlify.app` en lugar de `mintlify.cc`. -**Solución**: Actualiza la configuración de tu proxy inverso para que apunte a `.mintlify.dev` en lugar de `.mintlify.app`. +**Solución**: Actualiza la configuración de tu proxy inverso para que apunte a `.mintlify.cc` en lugar de `.mintlify.app`.
### Error 404 @@ -416,7 +416,7 @@ server { **Solución**: - Elimina el reenvío del encabezado `Host` -- Configura el encabezado `Origin` en tu subdominio de Mintlify (`mintlify.dev` para una subruta `/docs` o `mintlify.app` para una subruta diferente) +- Configura el encabezado `Origin` en tu subdominio de Mintlify (`mintlify.cc` para una subruta `/docs` o `mintlify.app` para una subruta diferente)
### Problemas de rendimiento diff --git a/es/deploy/route53-cloudfront.mdx b/es/deploy/route53-cloudfront.mdx index d65460e0fd..dae6d3d1e1 100644 --- a/es/deploy/route53-cloudfront.mdx +++ b/es/deploy/route53-cloudfront.mdx @@ -41,10 +41,10 @@ Todos los comportamientos (Behaviors) deben tener una **origin request policy** ![Página de CloudFront Distributions con el botón «Create distribution» resaltado.](/images/cloudfront/create-distribution.png) -3. En Origin domain, ingresa `[SUBDOMAIN].mintlify.dev`, donde `[SUBDOMAIN]` es el subdomain único de tu proyecto. +3. En Origin domain, ingresa `[SUBDOMAIN].mintlify.cc`, donde `[SUBDOMAIN]` es el subdomain único de tu proyecto. - ![Página «Create distribution» de CloudFront mostrando «acme.mintlify.dev» como Origin domain.](/images/cloudfront/origin-name.png) + ![Página «Create distribution» de CloudFront mostrando «acme.mintlify.cc» como Origin domain.](/images/cloudfront/origin-name.png) 4. En «Web Application Firewall (WAF)», habilita las protecciones de seguridad. @@ -92,7 +92,7 @@ A este punto, deberías tener dos Origins: uno con `[SUBDOMAIN].mintlify.app` y Los comportamientos en CloudFront permiten controlar la lógica de subrutas. A grandes rasgos, queremos implementar la siguiente lógica: -- **Si un usuario llega a tu subruta personalizada**, redirigir a `[SUBDOMAIN].mintlify.dev`. +- **Si un usuario llega a tu subruta personalizada**, redirigir a `[SUBDOMAIN].mintlify.cc`. - **Si un usuario llega a cualquier otra página**, redirigir a la página de inicio actual. 1. Ve a la pestaña "Behaviors" de tu distribución de CloudFront. @@ -125,21 +125,21 @@ Si `.well-known/*` es demasiado genérico, puede acotarse a un mínimo de 2 comp ### Tu subruta
-Crea un comportamiento con un **Path pattern** de la subruta que elijas, por ejemplo `/docs`, con **Origin and origin groups** apuntando a la URL `.mintlify.dev` (en nuestro caso `acme.mintlify.dev`). +Crea un comportamiento con un **Path pattern** de la subruta que elijas, por ejemplo `/docs`, con **Origin and origin groups** apuntando a la URL `.mintlify.cc` (en nuestro caso `acme.mintlify.cc`). - Establece "Cache policy" en **CachingOptimized**. - Establece "Origin request policy" en **AllViewerExceptHostHeader**. - Establece "Viewer protocol policy" en **Redirect HTTP to HTTPS**. - ![Página "Create behavior" de CloudFront con un "Path pattern" de "/docs/*" y "Origin and origin groups" apuntando a la URL `acme.mintlify.dev`.](/images/cloudfront/behavior-1.png) + ![Página "Create behavior" de CloudFront con un "Path pattern" de "/docs/*" y "Origin and origin groups" apuntando a la URL `acme.mintlify.cc`.](/images/cloudfront/behavior-1.png)
### Tu subruta con comodín
-Crea un comportamiento con un **Path pattern** que sea la subruta que elijas seguida de `/*`, por ejemplo `/docs/*`, y con **Origin and origin groups** apuntando a la misma URL `.mintlify.dev`. +Crea un comportamiento con un **Path pattern** que sea la subruta que elijas seguida de `/*`, por ejemplo `/docs/*`, y con **Origin and origin groups** apuntando a la misma URL `.mintlify.cc`. Esta configuración debe coincidir exactamente con el comportamiento de tu subruta base, con la excepción de **Path pattern**. diff --git a/es/deploy/vercel.mdx b/es/deploy/vercel.mdx index c2a99c99a5..72eb91918a 100644 --- a/es/deploy/vercel.mdx +++ b/es/deploy/vercel.mdx @@ -18,7 +18,7 @@ El archivo `vercel.json` configura cómo se compila e implementa tu proyecto. Se Usamos la configuración de `rewrites` en tu archivo `vercel.json` para enrutar las solicitudes desde tu dominio principal hacia tu documentación mediante un proxy. -Las reglas de reescritura (rewrites) asignan las solicitudes entrantes a distintos destinos sin cambiar la URL en el navegador. Cuando alguien visita `yoursite.com/docs`, Vercel obtiene internamente el contenido desde `your-subdomain.mintlify.dev/docs`, pero el usuario sigue viendo `yoursite.com/docs` en su navegador. Esto es diferente de las redirecciones, que envían a los usuarios a otra URL por completo. +Las reglas de reescritura (rewrites) asignan las solicitudes entrantes a distintos destinos sin cambiar la URL en el navegador. Cuando alguien visita `yoursite.com/docs`, Vercel obtiene internamente el contenido desde `your-subdomain.mintlify.cc/docs`, pero el usuario sigue viendo `yoursite.com/docs` en su navegador. Esto es diferente de las redirecciones, que envían a los usuarios a otra URL por completo.
## Configuración @@ -43,11 +43,11 @@ Las reglas de reescritura (rewrites) asignan las solicitudes entrantes a distint "rewrites": [ { "source": "/docs", - "destination": "https://[subdomain].mintlify.dev/docs" + "destination": "https://[subdomain].mintlify.cc/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlify.dev/docs/:match*" + "destination": "https://[subdomain].mintlify.cc/docs/:match*" } ] } diff --git a/fr/deploy/authentication-setup.mdx b/fr/deploy/authentication-setup.mdx index ed46445ae2..d05b62937a 100644 --- a/fr/deploy/authentication-setup.mdx +++ b/fr/deploy/authentication-setup.mdx @@ -11,7 +11,7 @@ keywords: ['authentication', 'auth', 'OAuth', 'JWT', 'password'] - L'authentification n'est disponible que pour la documentation hébergée sur un domaine personnalisé ou un sous-domaine Mintlify (par exemple, `docs.exemple.com` ou `exemple.mintlify.dev`). L'authentification **n'est pas prise en charge** lors de l'utilisation d'un [chemin de base personnalisé](/fr/deploy/docs-subpath) (par exemple, `exemple.com/docs`). + L'authentification n'est disponible que pour la documentation hébergée sur un domaine personnalisé ou un sous-domaine Mintlify (par exemple, `docs.exemple.com` ou `exemple.mintlify.cc`). L'authentification **n'est pas prise en charge** lors de l'utilisation d'un [chemin de base personnalisé](/fr/deploy/docs-subpath) (par exemple, `exemple.com/docs`). L’authentification exige que les utilisateurs se connectent avant d’accéder à votre documentation. diff --git a/fr/deploy/cloudflare.mdx b/fr/deploy/cloudflare.mdx index 4515005059..d93be95af5 100644 --- a/fr/deploy/cloudflare.mdx +++ b/fr/deploy/cloudflare.mdx @@ -76,7 +76,7 @@ async function handleRequest(request) { // Si la requête concerne le sous-chemin docs if (/^\/docs/.test(urlObject.pathname)) { // Alors rediriger via proxy vers Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.cc"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); @@ -169,7 +169,7 @@ Si vous utilisez Webflow pour héberger votre site principal et que vous souhait // Si la requête concerne le sous-chemin docs if (/^\/docs/.test(urlObject.pathname)) { // Proxy vers Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.cc"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); url.hostname = DOCS_URL; diff --git a/fr/deploy/csp-configuration.mdx b/fr/deploy/csp-configuration.mdx index 3ffa4d03fe..daf36cad3e 100644 --- a/fr/deploy/csp-configuration.mdx +++ b/fr/deploy/csp-configuration.mdx @@ -28,7 +28,7 @@ Les directives CSP suivantes contrôlent quelles ressources une page peut charge | Domaine | Finalité | Directive CSP | Obligatoire | |:-------|:--------|:--------------|:-------| | `d4tuoctqmanu0.cloudfront.net` | CSS et polices KaTeX | `style-src`, `font-src` | Obligatoire | -| `*.mintlify.dev` | Contenu de la documentation | `connect-src`, `frame-src` | Obligatoire | +| `*.mintlify.cc` | Contenu de la documentation | `connect-src`, `frame-src` | Obligatoire | | `*.mintlify.com` | Dashboard, API, proxy d’Analytics | `connect-src` | Obligatoire | | `leaves.mintlify.com` | API Assistant | `connect-src` | Obligatoire | | `d3gk2c5xim1je2.cloudfront.net` | Icônes, images, logos | `img-src` | Obligatoire | @@ -68,9 +68,9 @@ browser.sentry-cdn.com js.sentry-cdn.com hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; -connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com +connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com www.googletagmanager.com cdn.segment.com plausible.io us.posthog.com browser.sentry-cdn.com hcaptcha.com *.hcaptcha.com; -frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; +frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com; ``` @@ -94,7 +94,7 @@ Créez une règle de transformation des en-têtes de réponse : - **Header name**: `Content-Security-Policy` - **Header value**: ```text wrap - default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; + default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com; ``` 4. Déployez la règle. @@ -112,7 +112,7 @@ Ajoutez une stratégie d’en-têtes de réponse dans CloudFront : "Config": { "SecurityHeadersConfig": { "ContentSecurityPolicy": { - "ContentSecurityPolicy": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com;", + "ContentSecurityPolicy": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com;", "Override": true } } @@ -136,7 +136,7 @@ Ajoutez ceci à votre `vercel.json` : "headers": [ { "key": "Content-Security-Policy", - "value": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com;" + "value": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com;" } ] } diff --git a/fr/deploy/reverse-proxy.mdx b/fr/deploy/reverse-proxy.mdx index 7f7785fba6..778c5ce1c0 100644 --- a/fr/deploy/reverse-proxy.mdx +++ b/fr/deploy/reverse-proxy.mdx @@ -14,7 +14,7 @@ Lorsque vous mettez en place un proxy inverse, surveillez les problèmes potenti Mintlify prend en charge deux configurations de proxy inverse en fonction de vos exigences en matière de sous-chemin. -- **Héberger sur `/docs`** : utilisez `mintlify.dev` comme cible du proxy. Activez le bouton **Héberger sur `/docs`** sur la page [Configuration du domaine personnalisé](https://dashboard.mintlify.com/settings/deployment/custom-domain) de votre Dashboard. Il s’agit d’une configuration plus simple avec moins de routes. +- **Héberger sur `/docs`** : utilisez `mintlify.cc` comme cible du proxy. Activez le bouton **Héberger sur `/docs`** sur la page [Configuration du domaine personnalisé](https://dashboard.mintlify.com/settings/deployment/custom-domain) de votre Dashboard. Il s’agit d’une configuration plus simple avec moins de routes. - **Sous-chemin personnalisé** : utilisez `mintlify.app` comme cible du proxy. Cette approche prend en charge n’importe quel sous-chemin et nécessite des règles de routage supplémentaires.
@@ -30,7 +30,7 @@ Avant de configurer votre reverse proxy : 3. Saisissez votre domaine et sélectionnez **Add domain**. - Lorsque vous activez **Host at `/docs`**, l’URL canonique de votre documentation devient `.mintlify.dev`. L’invalidation du cache s’arrête sur `mintlify.app`, et vous devez configurer le proxy vers `mintlify.dev` pour que les mises à jour apparaissent. + Lorsque vous activez **Host at `/docs`**, l’URL canonique de votre documentation devient `.mintlify.cc`. L’invalidation du cache s’arrête sur `mintlify.app`, et vous devez configurer le proxy vers `mintlify.cc` pour que les mises à jour apparaissent.
@@ -41,14 +41,14 @@ Redirigez ces chemins via un proxy vers votre sous-domaine Mintlify : | Path | Destination | Caching | | --------------------------------- | ------------------------------------ | -------- | -| `/docs` | `.mintlify.dev/docs` | No cache | -| `/docs/*` | `.mintlify.dev/docs` | No cache | -| `/.well-known/vercel/*` | `.mintlify.dev` | No cache | -| `/.well-known/skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/.well-known/agent-skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/skill.md` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms.txt` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms-full.txt` (optional) | `.mintlify.dev/docs` | No cache | +| `/docs` | `.mintlify.cc/docs` | No cache | +| `/docs/*` | `.mintlify.cc/docs` | No cache | +| `/.well-known/vercel/*` | `.mintlify.cc` | No cache | +| `/.well-known/skills/*` (optional) | `.mintlify.cc/docs` | No cache | +| `/.well-known/agent-skills/*` (optional) | `.mintlify.cc/docs` | No cache | +| `/skill.md` (optional) | `.mintlify.cc/docs` | No cache | +| `/llms.txt` (optional) | `.mintlify.cc/docs` | No cache | +| `/llms-full.txt` (optional) | `.mintlify.cc/docs` | No cache | Les routes `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, `/llms.txt` et `/llms-full.txt` sont facultatives. Ne les incluez que si vous souhaitez servir des fichiers d'IA sur des chemins à la racine comme `your-domain.com/llms.txt` plutôt que sous votre sous-chemin de documentation, par exemple `your-domain.com/docs/llms.txt`. @@ -58,7 +58,7 @@ Les routes `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, Configurez votre reverse proxy avec les en-têtes suivants : -* **Origin** : contient le sous-domaine cible `.mintlify.dev` +* **Origin** : contient le sous-domaine cible `.mintlify.cc` * **X-Forwarded-For** : conserve les informations d’adresse IP du client * **X-Forwarded-Proto** : conserve le protocole d’origine (HTTP/HTTPS) * **X-Real-IP** : transmet la véritable adresse IP du client @@ -79,8 +79,8 @@ server { # Vercel verification paths location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.dev; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -91,8 +91,8 @@ server { # AI skills paths location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -103,8 +103,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -115,8 +115,8 @@ server { # Manifeste de compétence (facultatif) location = /skill.md { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -127,8 +127,8 @@ server { # Fichiers d'index LLM (facultatif) location = /llms.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -138,8 +138,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -150,8 +150,8 @@ server { # Documentation root location = /docs { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -162,8 +162,8 @@ server { # All documentation paths location /docs/ { - proxy_pass https://.mintlify.dev/docs/; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs/; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -403,9 +403,9 @@ server { **Symptômes** : Vous publiez des mises à jour de la documentation, mais les modifications n'apparaissent pas sur votre site. -**Cause** : Vous avez activé **Host at `/docs`** dans votre Dashboard, mais votre proxy inverse pointe vers `mintlify.app` au lieu de `mintlify.dev`. +**Cause** : Vous avez activé **Host at `/docs`** dans votre Dashboard, mais votre proxy inverse pointe vers `mintlify.app` au lieu de `mintlify.cc`. -**Solution** : Mettez à jour la configuration de votre proxy inverse pour qu'il pointe vers `.mintlify.dev` au lieu de `.mintlify.app`. +**Solution** : Mettez à jour la configuration de votre proxy inverse pour qu'il pointe vers `.mintlify.cc` au lieu de `.mintlify.app`.
### Erreur 404 @@ -418,7 +418,7 @@ server { **Solution** : - Supprimer le transfert de l’en-tête `Host` -- Définir l’en-tête `Origin` sur votre sous-domaine Mintlify (`mintlify.dev` pour un sous-chemin `/docs` ou `mintlify.app` pour un autre sous-chemin) +- Définir l’en-tête `Origin` sur votre sous-domaine Mintlify (`mintlify.cc` pour un sous-chemin `/docs` ou `mintlify.app` pour un autre sous-chemin)
### Problèmes de performances diff --git a/fr/deploy/route53-cloudfront.mdx b/fr/deploy/route53-cloudfront.mdx index 0fe8c37dfb..60858d65c3 100644 --- a/fr/deploy/route53-cloudfront.mdx +++ b/fr/deploy/route53-cloudfront.mdx @@ -40,10 +40,10 @@ Tous les Behaviors doivent avoir une **origin request policy** de `AllViewerExce ![Page des distributions CloudFront avec le bouton « Create distribution » mis en évidence.](/images/cloudfront/create-distribution.png) -3. Pour le domaine d’origine, saisissez `[SUBDOMAIN].mintlify.dev`, où `[SUBDOMAIN]` est le sous-domaine propre à votre projet. +3. Pour le domaine d’origine, saisissez `[SUBDOMAIN].mintlify.cc`, où `[SUBDOMAIN]` est le sous-domaine propre à votre projet. - ![Page « Create distribution » de CloudFront affichant « acme.mintlify.dev » comme domaine d’origine.](/images/cloudfront/origin-name.png) + ![Page « Create distribution » de CloudFront affichant « acme.mintlify.cc » comme domaine d’origine.](/images/cloudfront/origin-name.png) 4. Pour « Web Application Firewall (WAF) », activez les protections de sécurité. @@ -91,7 +91,7 @@ Tous les Behaviors doivent avoir une **origin request policy** de `AllViewerExce Les comportements dans CloudFront permettent de contrôler la logique des sous-chemins. Globalement, nous voulons mettre en place la logique suivante : -- **Si un utilisateur arrive sur votre sous-chemin personnalisé**, le rediriger vers `[SUBDOMAIN].mintlify.dev`. +- **Si un utilisateur arrive sur votre sous-chemin personnalisé**, le rediriger vers `[SUBDOMAIN].mintlify.cc`. - **Si un utilisateur arrive sur une autre page**, le diriger vers la page d’accueil actuelle. 1. Accédez à l’onglet « Behaviors » de votre distribution CloudFront. @@ -124,21 +124,21 @@ Si `/.well-known/*` est trop générique, vous pouvez le restreindre à au moins ### Votre sous-chemin
-Créez un comportement avec un **Path pattern** défini sur le sous-chemin de votre choix, par exemple `/docs`, avec **Origin and origin groups** pointant vers l’URL `.mintlify.dev` (dans notre cas `acme.mintlify.dev`). +Créez un comportement avec un **Path pattern** défini sur le sous-chemin de votre choix, par exemple `/docs`, avec **Origin and origin groups** pointant vers l’URL `.mintlify.cc` (dans notre cas `acme.mintlify.cc`). - Définissez « Cache policy » sur **CachingOptimized**. - Définissez « Origin request policy » sur **AllViewerExceptHostHeader**. - Définissez « Viewer Protocol Policy » sur **Redirect HTTP to HTTPS**. - ![Page CloudFront « Create behavior » avec un « Path pattern » de « /docs/* » et « Origin and origin groups » pointant vers l’URL `acme.mintlify.dev`.](/images/cloudfront/behavior-1.png) + ![Page CloudFront « Create behavior » avec un « Path pattern » de « /docs/* » et « Origin and origin groups » pointant vers l’URL `acme.mintlify.cc`.](/images/cloudfront/behavior-1.png)
### Votre sous-chemin avec caractère générique
-Créez un comportement avec un **Path pattern** correspondant au sous-chemin de votre choix suivi de `/*`, par exemple `/docs/*`, et des **Origin and origin groups** pointant vers la même URL en `.mintlify.dev`. +Créez un comportement avec un **Path pattern** correspondant au sous-chemin de votre choix suivi de `/*`, par exemple `/docs/*`, et des **Origin and origin groups** pointant vers la même URL en `.mintlify.cc`. Ces paramètres doivent correspondre exactement au comportement de votre sous-chemin de base, à l’exception du **Path pattern**. diff --git a/fr/deploy/vercel.mdx b/fr/deploy/vercel.mdx index 35b30df353..661c13928f 100644 --- a/fr/deploy/vercel.mdx +++ b/fr/deploy/vercel.mdx @@ -18,7 +18,7 @@ Le fichier `vercel.json` définit la façon dont votre projet est construit et d Nous utilisons la configuration `rewrites` dans votre fichier `vercel.json` pour faire transiter les requêtes de votre domaine principal vers votre documentation via un proxy. -Les réécritures (`rewrites`) font correspondre les requêtes entrantes à différentes destinations sans modifier l'URL dans le navigateur. Quand quelqu’un visite `yoursite.com/docs`, Vercel récupère en interne le contenu depuis `your-subdomain.mintlify.dev/docs`, mais l’utilisateur voit toujours `yoursite.com/docs` dans son navigateur. Cela diffère des redirections, qui envoient les utilisateurs vers une URL complètement différente. +Les réécritures (`rewrites`) font correspondre les requêtes entrantes à différentes destinations sans modifier l'URL dans le navigateur. Quand quelqu’un visite `yoursite.com/docs`, Vercel récupère en interne le contenu depuis `your-subdomain.mintlify.cc/docs`, mais l’utilisateur voit toujours `yoursite.com/docs` dans son navigateur. Cela diffère des redirections, qui envoient les utilisateurs vers une URL complètement différente.
## Configuration @@ -43,11 +43,11 @@ Les réécritures (`rewrites`) font correspondre les requêtes entrantes à diff "rewrites": [ { "source": "/docs", - "destination": "https://[subdomain].mintlify.dev/docs" + "destination": "https://[subdomain].mintlify.cc/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlify.dev/docs/:match*" + "destination": "https://[subdomain].mintlify.cc/docs/:match*" } ] } diff --git a/zh/deploy/authentication-setup.mdx b/zh/deploy/authentication-setup.mdx index cc871cfcf7..345ede73f6 100644 --- a/zh/deploy/authentication-setup.mdx +++ b/zh/deploy/authentication-setup.mdx @@ -11,7 +11,7 @@ keywords: ['authentication', 'auth', 'OAuth', 'JWT', 'password'] - 认证仅适用于托管在自定义域名或 Mintlify 子域名上的文档（例如 `docs.example.com` 或 `example.mintlify.dev`）。使用[自定义基础路径](/zh/deploy/docs-subpath)（例如 `example.com/docs`）时**不支持**认证功能。 + 认证仅适用于托管在自定义域名或 Mintlify 子域名上的文档（例如 `docs.example.com` 或 `example.mintlify.cc`）。使用[自定义基础路径](/zh/deploy/docs-subpath)（例如 `example.com/docs`）时**不支持**认证功能。 启用认证后，用户需先登录才能访问你的文档。 diff --git a/zh/deploy/cloudflare.mdx b/zh/deploy/cloudflare.mdx index 667cce21d4..326ee38e74 100644 --- a/zh/deploy/cloudflare.mdx +++ b/zh/deploy/cloudflare.mdx @@ -76,7 +76,7 @@ async function handleRequest(request) { // 如果请求是 docs 子路径 if (/^\/docs/.test(urlObject.pathname)) { // 然后代理到 Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.cc"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); @@ -169,7 +169,7 @@ async function handleRequest(request) { // 如果请求是文档子路径 if (/^\/docs/.test(urlObject.pathname)) { // 代理到 Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.cc"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); url.hostname = DOCS_URL; diff --git a/zh/deploy/csp-configuration.mdx b/zh/deploy/csp-configuration.mdx index 0971b3e6e6..b4a37a3f79 100644 --- a/zh/deploy/csp-configuration.mdx +++ b/zh/deploy/csp-configuration.mdx @@ -28,7 +28,7 @@ keywords: ["内容安全策略", "CSP", "指令", "安全标头", "防火墙", " | 域名 | 用途 | CSP 指令 | 是否必需 | |:-------|:--------|:--------------|:-------| | `d4tuoctqmanu0.cloudfront.net` | KaTeX CSS、字体 | `style-src`, `font-src` | 必需 | -| `*.mintlify.dev` | 文档内容 | `connect-src`, `frame-src` | 必需 | +| `*.mintlify.cc` | 文档内容 | `connect-src`, `frame-src` | 必需 | | `*.mintlify.com` | 控制台、API、分析代理 | `connect-src` | 必需 | | `leaves.mintlify.com` | AI 助手 API | `connect-src` | 必需 | | `d3gk2c5xim1je2.cloudfront.net` | 图标、图像、徽标 | `img-src` | 必需 | @@ -68,9 +68,9 @@ browser.sentry-cdn.com js.sentry-cdn.com hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; -connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com +connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com www.googletagmanager.com cdn.segment.com plausible.io us.posthog.com browser.sentry-cdn.com hcaptcha.com *.hcaptcha.com; -frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; +frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com; ``` @@ -94,7 +94,7 @@ frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; - **Header name**：`Content-Security-Policy` - **Header value**： ```text wrap - default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; + default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com; ``` 4. 部署该规则。 @@ -112,7 +112,7 @@ frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; "Config": { "SecurityHeadersConfig": { "ContentSecurityPolicy": { - "ContentSecurityPolicy": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com;", + "ContentSecurityPolicy": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com;", "Override": true } } @@ -136,7 +136,7 @@ frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; "headers": [ { "key": "Content-Security-Policy", - "value": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com;" + "value": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.cc *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.cc hcaptcha.com *.hcaptcha.com;" } ] } diff --git a/zh/deploy/reverse-proxy.mdx b/zh/deploy/reverse-proxy.mdx index 657199ced6..00ef86326f 100644 --- a/zh/deploy/reverse-proxy.mdx +++ b/zh/deploy/reverse-proxy.mdx @@ -18,7 +18,7 @@ keywords: ["反向代理配置", "nginx", "代理路由", "请求头转发"] Mintlify 根据你的子路径需求支持两种反向代理配置。 -- **在 `/docs` 下托管**：使用 `mintlify.dev` 作为代理目标。在控制台的 [Custom domain setup](https://dashboard.mintlify.com/settings/deployment/custom-domain) 页面中开启 **Host at `/docs`** 开关。这种方式路由更少，配置更简单。 +- **在 `/docs` 下托管**：使用 `mintlify.cc` 作为代理目标。在控制台的 [Custom domain setup](https://dashboard.mintlify.com/settings/deployment/custom-domain) 页面中开启 **Host at `/docs`** 开关。这种方式路由更少，配置更简单。 - **自定义子路径**：使用 `mintlify.app` 作为代理目标。这种方式支持任意子路径，但需要额外的路由规则。
@@ -34,7 +34,7 @@ Mintlify 根据你的子路径需求支持两种反向代理配置。 3. 输入你的 domain 并选择 **Add domain**。 - 当你启用 **Host at `/docs`** 时，你的文档规范 URL 将变为 `.mintlify.dev`。在 `mintlify.app` 上的缓存失效将停止，你必须将代理指向 `mintlify.dev`，更新才会生效。 + 当你启用 **Host at `/docs`** 时，你的文档规范 URL 将变为 `.mintlify.cc`。在 `mintlify.app` 上的缓存失效将停止，你必须将代理指向 `mintlify.cc`，更新才会生效。
@@ -45,14 +45,14 @@ Mintlify 根据你的子路径需求支持两种反向代理配置。 | 路径 | 目标地址 | 缓存 | | --------------------------------- | ------------------------------------ | -------- | -| `/docs` | `.mintlify.dev/docs` | No cache | -| `/docs/*` | `.mintlify.dev/docs` | No cache | -| `/.well-known/vercel/*` | `.mintlify.dev` | No cache | -| `/.well-known/skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/.well-known/agent-skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/skill.md` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms.txt` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms-full.txt` (optional) | `.mintlify.dev/docs` | No cache | +| `/docs` | `.mintlify.cc/docs` | No cache | +| `/docs/*` | `.mintlify.cc/docs` | No cache | +| `/.well-known/vercel/*` | `.mintlify.cc` | No cache | +| `/.well-known/skills/*` (optional) | `.mintlify.cc/docs` | No cache | +| `/.well-known/agent-skills/*` (optional) | `.mintlify.cc/docs` | No cache | +| `/skill.md` (optional) | `.mintlify.cc/docs` | No cache | +| `/llms.txt` (optional) | `.mintlify.cc/docs` | No cache | +| `/llms-full.txt` (optional) | `.mintlify.cc/docs` | No cache | `/.well-known/skills/*`、`/.well-known/agent-skills/*`、`/skill.md`、`/llms.txt` 和 `/llms-full.txt` 这些路由是可选的。只有当你希望在站点根路径（例如 `your-domain.com/llms.txt`）而不是在文档子路径下（例如 `your-domain.com/docs/llms.txt`）提供 AI 文件时，才需要包含它们。 @@ -62,7 +62,7 @@ Mintlify 根据你的子路径需求支持两种反向代理配置。 按以下请求头要求配置你的反向代理： -* **Origin**：包含目标子域 `.mintlify.dev` +* **Origin**：包含目标子域 `.mintlify.cc` * **X-Forwarded-For**：保留客户端 IP 信息 * **X-Forwarded-Proto**：保留原始协议 (HTTP/HTTPS) * **X-Real-IP**：转发真实的客户端 IP 地址 @@ -83,8 +83,8 @@ server { # Vercel 验证路径 location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.dev; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -95,8 +95,8 @@ server { # AI 技能路径 location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -107,8 +107,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -119,8 +119,8 @@ server { # 技能清单(可选) location = /skill.md { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -131,8 +131,8 @@ server { # LLM 索引文件(可选) location = /llms.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -142,8 +142,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -154,8 +154,8 @@ server { # 文档根路径 location = /docs { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -166,8 +166,8 @@ server { # 所有文档路径 location /docs/ { - proxy_pass https://.mintlify.dev/docs/; - proxy_set_header Origin .mintlify.dev; + proxy_pass https://.mintlify.cc/docs/; + proxy_set_header Origin .mintlify.cc; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -401,9 +401,9 @@ server { **症状**：你发布了文档更新，但这些更改并没有在你的网站上显示出来。 -**原因**：你在控制台中启用了 **Host at `/docs`**，但你的反向代理指向的是 `mintlify.app` 而不是 `mintlify.dev`。 +**原因**：你在控制台中启用了 **Host at `/docs`**，但你的反向代理指向的是 `mintlify.app` 而不是 `mintlify.cc`。 -**解决方案**：将反向代理配置更新为指向 `.mintlify.dev`，而不是 `.mintlify.app`。 +**解决方案**：将反向代理配置更新为指向 `.mintlify.cc`，而不是 `.mintlify.app`。
### 404 错误 @@ -416,7 +416,7 @@ server { **解决方案**： - 停止转发 `Host` 头 -- 将 `Origin` 头设置为你的 Mintlify 子域（对于 `/docs` 子路径使用 `mintlify.dev`，其他子路径使用 `mintlify.app`） +- 将 `Origin` 头设置为你的 Mintlify 子域（对于 `/docs` 子路径使用 `mintlify.cc`，其他子路径使用 `mintlify.app`）
### 性能问题 diff --git a/zh/deploy/route53-cloudfront.mdx b/zh/deploy/route53-cloudfront.mdx index b868fe6a89..c33f411efe 100644 --- a/zh/deploy/route53-cloudfront.mdx +++ b/zh/deploy/route53-cloudfront.mdx @@ -40,10 +40,10 @@ import Propagating from "/snippets/zh/custom-subpath-propagating.mdx"; ![CloudFront Distributions 页面，高亮显示 “Create distribution” 按钮。](/images/cloudfront/create-distribution.png) -3. 在 Origin domain 中输入 `[SUBDOMAIN].mintlify.dev`，其中 `[SUBDOMAIN]` 是你项目的唯一子域。 +3. 在 Origin domain 中输入 `[SUBDOMAIN].mintlify.cc`，其中 `[SUBDOMAIN]` 是你项目的唯一子域。 - ![CloudFront “Create distribution” 页面显示 “acme.mintlify.dev” 作为 Origin domain。](/images/cloudfront/origin-name.png) + ![CloudFront “Create distribution” 页面显示 “acme.mintlify.cc” 作为 Origin domain。](/images/cloudfront/origin-name.png) 4. 在 “Web Application Firewall (WAF)” 中，启用安全防护。 @@ -91,7 +91,7 @@ import Propagating from "/snippets/zh/custom-subpath-propagating.mdx"; CloudFront 中的行为用于控制子路径逻辑。总体而言，我们希望实现以下逻辑： -- **如果用户访问你的自定义子路径**，跳转到 `[SUBDOMAIN].mintlify.dev`。 +- **如果用户访问你的自定义子路径**，跳转到 `[SUBDOMAIN].mintlify.cc`。 - **如果用户访问其他任意页面**，跳转到当前登录页。 1. 打开 CloudFront 分配的 “Behaviors” 标签页。 @@ -124,21 +124,21 @@ CloudFront 中的行为用于控制子路径逻辑。总体而言，我们希望 ### 你的子路径
-创建一个行为，将 **Path pattern** 设置为你选择的子路径，例如 `/docs`，并将 **Origin and origin groups** 指向 `.mintlify.dev` 的 URL（在我们的示例中为 `acme.mintlify.dev`）。 +创建一个行为，将 **Path pattern** 设置为你选择的子路径，例如 `/docs`，并将 **Origin and origin groups** 指向 `.mintlify.cc` 的 URL（在我们的示例中为 `acme.mintlify.cc`）。 - 将 "Cache policy" 设置为 **CachingOptimized**。 - 将 "Origin request policy" 设置为 **AllViewerExceptHostHeader**。 - 将 "Viewer Protocol Policy" 设置为 **Redirect HTTP to HTTPS**。 - ![CloudFront 的 "Create behavior" 页面，其中 "Path pattern" 设置为 "/docs/*"，并且 "Origin and origin groups" 指向 `acme.mintlify.dev` 的 URL。](/images/cloudfront/behavior-1.png) + ![CloudFront 的 "Create behavior" 页面，其中 "Path pattern" 设置为 "/docs/*"，并且 "Origin and origin groups" 指向 `acme.mintlify.cc` 的 URL。](/images/cloudfront/behavior-1.png)
### 带通配符的子路径
-创建一个行为，在 **Path pattern** 中填写你选择的子路径并在后面添加 `/*`，例如 `/docs/*`，并将 **Origin and origin groups** 指向相同的 `.mintlify.dev` URL。 +创建一个行为，在 **Path pattern** 中填写你选择的子路径并在后面添加 `/*`，例如 `/docs/*`，并将 **Origin and origin groups** 指向相同的 `.mintlify.cc` URL。 除 **Path pattern** 外，其余设置应与基础子路径行为完全一致。 diff --git a/zh/deploy/vercel.mdx b/zh/deploy/vercel.mdx index 99d93c22ea..aef7fc59e1 100644 --- a/zh/deploy/vercel.mdx +++ b/zh/deploy/vercel.mdx @@ -18,7 +18,7 @@ import { VercelJsonGenerator } from "/snippets/zh/vercel-json-generator.mdx"; 我们会在你的 `vercel.json` 文件中使用 `rewrites` 配置，将来自主域名的请求代理到你的文档站点。 -Rewrites 会在不更改浏览器中 URL 的情况下，将传入请求映射到不同的目标。当有人访问 `yoursite.com/docs` 时，Vercel 会在内部从 `your-subdomain.mintlify.dev/docs` 获取内容，但用户在浏览器中仍然看到的是 `yoursite.com/docs`。这与重定向不同，后者会将用户直接带到另一个完全不同的 URL。 +Rewrites 会在不更改浏览器中 URL 的情况下，将传入请求映射到不同的目标。当有人访问 `yoursite.com/docs` 时，Vercel 会在内部从 `your-subdomain.mintlify.cc/docs` 获取内容，但用户在浏览器中仍然看到的是 `yoursite.com/docs`。这与重定向不同，后者会将用户直接带到另一个完全不同的 URL。
## 配置 @@ -43,11 +43,11 @@ Rewrites 会在不更改浏览器中 URL 的情况下，将传入请求映射到 "rewrites": [ { "source": "/docs", - "destination": "https://[subdomain].mintlify.dev/docs" + "destination": "https://[subdomain].mintlify.cc/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlify.dev/docs/:match*" + "destination": "https://[subdomain].mintlify.cc/docs/:match*" } ] }