Josh
c602b8f8f3
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.
kb.anhonesthost.com
The An Honest Host knowledge base — customer documentation for WHP (our hosting platform) and related services.
Live at: https://kb.anhonesthost.com
Run locally
Requires Node 20+ (we test on 22).
npm install
npm run dev
# open http://localhost:4321
To expose the dev server on a different host/port (useful inside containers):
npm run dev -- --host 0.0.0.0 --port 8080
Adding or editing a doc
See CONTRIBUTING.md — it covers the page template, where files live, and how PRs are reviewed.
How it deploys
Push to main triggers a Gitea Actions workflow that builds the site and uploads it via SFTP to the production WHP site. No manual deploy step.
Licence
Content: CC BY 4.0. Build config and scripts: MIT (see source headers if any).