fix(Docs): rephrase custom domains to custom domain

This commit is contained in:
cheskoxd 2025-09-03 19:32:44 -05:00
parent 53b07dddb7
commit 0c06d34632
6 changed files with 8 additions and 8 deletions

View File

@ -126,7 +126,7 @@
</script>
<div class="max-w-2xl">
<CardHeader documentation={`/docs/custom-domains`}>Custom Domain (CNAME)</CardHeader>
<CardHeader documentation={`/docs/custom-domain`}>Custom Domain (CNAME)</CardHeader>
<div class="mb-8">Use a custom domain (CNAME) with your PocketHost instance.</div>
{#if cname && regex.test(formCname.trim())}

View File

@ -74,7 +74,7 @@
<DocLink path="versions" title="Changing Versions" />
<DocLink path="s3" title="Using S3 Storage" />
<DocLink path="custom-binaries" title="Custom Binaries" />
<DocLink path="custom-domains" title="Custom Domains" />
<DocLink path="custom-domain" title="Custom Domain" />
<DocLink path="backup-restore" title="Backup/Restore" />
<li class="menu-title">Daily Use Guide</li>

View File

@ -10,6 +10,6 @@ Each PocketHost instance is assigned a permanent UUID, and a unique subdomain th
> **Example:** I use PocketHost to run the backend for my web game, Harvest. I created a PocketHost instance and chose the subdomain `harvest`, making it accessible at `https://harvest.pockethost.io`. Since instances can be [renamed](/docs/rename-instance/), PocketHost also assigns a permanent UUID. In this case, the UUID is `mfsicdp6ia1zpiu`, so the instance is always accessible at `https://mfsicdp6ia1zpiu.pockethost.io`, regardless of subdomain changes.
Custom domains are supported at the Pro level, and we manage SSL certificates for you. Learn more about setting up custom domains [here](/docs/custom-domains).
Custom domains are supported at the Pro level, and we manage SSL certificates for you. Learn more about setting up custom domains [here](/docs/custom-domain).
For direct file access, you can use [FTP access](/docs/ftp) to manage files like backups, uploads, and logs directly on your instance.

View File

@ -1,6 +1,6 @@
# Custom Domains
# Custom Domain
PocketHost instances can use custom domains instead of the default `*.pockethost.io` subdomain. There are no limits on the number of domains you can add to an instance.
PocketHost instances can use a custom domain instead of the default `*.pockethost.io` subdomain.
## How It Works
@ -25,7 +25,7 @@ Create a CNAME record with your DNS provider:
1. Navigate to your instance in the PocketHost Dashboard
2. Go to the **Settings** tab
3. Add your custom domain in the custom domains section
3. Add your custom domain in the custom domain section
4. PocketHost will automatically begin verification
### Step 3: Verification
@ -34,7 +34,7 @@ PocketHost uses Cloudflare's HTTP verification system to confirm domain ownershi
You can check the status anytime in your dashboard or click the refresh button to manually trigger a verification check.
## Static Files and Custom Domains
## Static Files and Custom Domain
All static files in your instance's `pb_public` directory will be served through your custom domain over HTTPS, making it perfect for static sites and assets.

View File

@ -44,7 +44,7 @@ export const features = [
description: `Access to private support channels on <a href="${DISCORD_URL}" class="link">Discord</a>.`,
},
{
title: 'Custom Domains',
title: 'Custom Domain',
description: 'Seamless custom domain integration for your PocketHost instances.',
},
{