docs: verify against real WHP + capture real screenshots

Discovery against the demo account on whp01 surfaced several inaccuracies:

- Cache is Valkey (Redis wire-compatible), not Redis or Memcached.
  No Memcached is offered as a separate service.
- Site Monitoring is the sidebar label (not 'AI Monitor').
- 'Add a domain' has no Primary/Add-on distinction.
- Sites form: 'Container Type' (not 'Site type'), Number of Containers
  (1-10 for horizontal scaling), CPU per Container (default 0.25),
  Memory per Container (default 256MB), SSL inline on the same form.
- Backups: default retention 5 days / 10 backups; on-demand + scheduled;
  S3 backup targets are visible and configurable.
- Email: per-domain settings live behind 'Setup Instructions' on the
  Email page; mail server hostname is on the Dashboard (per-server,
  e.g. mail01.cloud-hosting.io), not per-domain.

Also reworked the screenshot pipeline:
- New shots.config.ts targets the real index.php?page=... URLs
- Added redactSensitive() step that runs before each screenshot to swap
  server names, IPs, mail hostnames, and demo-user-isms with neutral
  placeholders. This keeps docs portable across the fleet.
- Hides .brand-full and .navbar-text (top-bar server identifier and
  Welcome greeting).
- Captured 9 real WHP screenshots; removed stale placeholders.
This commit is contained in:
2026-05-17 17:00:13 -07:00
parent 53bc37fd0d
commit c602b8f8f3
32 changed files with 460 additions and 152 deletions
@@ -1,6 +1,6 @@
---
title: Service hostnames
description: Quick reference for connecting to MySQL, PostgreSQL, Memcached, and Redis from inside your container.
description: Quick reference for connecting to MySQL, PostgreSQL, and Valkey from inside your container.
sidebar:
order: 1
---
@@ -14,24 +14,23 @@ Use these hostnames from inside your WHP container — they resolve to the inter
## Where do I get credentials?
Each service's credentials live in a different section of the WHP panel:
- **MySQL** → **Databases → MySQL → Users**
- **PostgreSQL** → **Databases → PostgreSQL** (if enabled on your plan)
- **Redis** → **Caching → Redis**
- **Memcached** — no auth required; the service is isolated per container.
- **MySQL** — sidebar → **MySQL Management**. Create users and databases there; the **phpMyAdmin** link below it opens an SSO'd phpMyAdmin in a new tab.
- **PostgreSQL** — sidebar → **PostgreSQL**. Same shape as MySQL Management; the **Adminer** link below it opens an SSO'd Adminer.
- **Valkey** — sidebar → **Valkey Cache**. Click **Enable Valkey**, pick a memory cap and mode, and you're done — no password needed because connections are network-isolated to your account.
## Mail servers
Mail server hostnames are **per-domain**, not a single shared hostname. Find the exact IMAP / POP3 / SMTP hostnames for each domain on the **Dashboard** page in WHP.
Mail server hostnames are not per-domain. Your server has one mail server hostname (for example `mail01.cloud-hosting.io`) that handles IMAP, POP3, and SMTP for every domain on that server. Find your exact mail server hostname on the **Dashboard** page in WHP under **Server Information** — that's also where you'll find your server's IP, primary nameservers, and your home directory.
For step-by-step email-client setup, the Email page has a **Setup Instructions** button that lays out the exact host, port, and security settings.
## Connecting from your laptop
Direct external connections to these internal services are not exposed for security reasons. Use the panel's tools instead:
Direct external connections to these internal services are not exposed. Use the panel's tools instead:
- **MySQL** — **phpMyAdmin** in the panel for ad-hoc queries.
- **PostgreSQL** — **Adminer** in the panel.
- **Redis / Memcached** — use the **Caching** section's built-in CLI panel.
- **Valkey** — there's no first-party browser tool; use a Valkey/Redis client inside your site's **Terminal** (sidebar → **Terminal**).
## Related