cloud-hosting-platform/kb-anhonesthost
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: verify against real WHP + capture real screenshots

Browse Source 
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:
Josh
2026-05-17 17:00:13 -07:00
parent 53bc37fd0d
commit c602b8f8f3
32 changed files with 460 additions and 152 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/content/docs/whp/add-ons/archival-email.mdx
+8 -10
View File
@@ -18,6 +18,8 @@ Archival email keeps a long-term, searchable copy of your mail **outside** the l
- Compliance or policy requires you keep email for a fixed window.
- You want a recovery option for mail you accidentally delete from the live mailbox.
It's powered by our [Bichon](https://anhonesthost.com/bichon/) archival service.
## How it's different from backups
| | Backups | Archival email |
@@ -30,22 +32,18 @@ You can use both — they cover different problems.
## What's included
- **Per-mailbox archive** — enable on the mailboxes that need it, not the whole account.
- **14-day quick-restore window** — accidentally deleted mail is recoverable without staff help.
- **Configurable longer retention** — set retention to match your policy.
- **Independent password reset** on the archive without touching the live mailbox — so you can grant audit access without disturbing the user.
- **Per-mailbox archive.** Enable on the mailboxes that need it, not the whole account. Your plan has an **archival slots** quota; the Email page shows current usage (e.g. `Archival: 0 of 0 mailboxes archived (no archival slots in your plan)` if you haven't added the add-on yet).
- **14-day quick-restore window.** Accidentally deleted mail is recoverable without staff help.
- **Configurable longer retention.** Set retention to match your policy.
- **Independent password reset on the archive.** Grant audit access without disturbing the live mailbox.
## How to enable
From the [client portal](https://secure.anhonesthost.com/clientarea.php), open **Add-ons** under your hosting service and pick Archival email. Billing is per archived mailbox.
## How to search archived mail
## How to use it
In WHP, go to the sidebar: **Email → Archive**. Pick the mailbox, then search by date range, sender, subject, or body content.
![WHP Email Archive page](~/assets/screenshots/whp/whp-email-archive.png)
Click a result to view the message in place; click **Restore to mailbox** to send it back to the live mailbox.
The archive is managed alongside your regular mailboxes on the **Email** page in WHP — the **Email Accounts** section shows archive status per mailbox, and the per-mailbox menu lets you search and restore archived mail.
## Related
src/content/docs/whp/add-ons/monitoring.mdx
+9 -7
View File
@@ -1,5 +1,5 @@
---
title: Monitoring (AI Monitor)
title: Site Monitoring
description: Proactive alerts for site errors, brute-force attempts, and exploit signatures.
sidebar:
order: 2
@@ -12,9 +12,9 @@ import Support from '~/content/partials/support-link.mdx';
## What it does
AI Monitor watches your site's logs, error rates, and access patterns in the background. If something looks unusual — a sustained spike in 500 errors, a brute-force pattern against a login page, a request matching a known exploit signature — you get an alert.
Site Monitoring watches your site's logs, error rates, and access patterns in the background. If something looks unusual — a sustained spike in 500 errors, a brute-force pattern against a login page, a request matching a known exploit signature — you get an alert.
By default alerts go to the contact email on your account; SMS is available for critical-severity events if you opt in.
By default, alerts go to the contact email on your account. SMS is available for critical-severity events if you opt in.
## What's included
@@ -26,15 +26,17 @@ By default alerts go to the contact email on your account; SMS is available for
## How to enable
From the [client portal](https://secure.anhonesthost.com/clientarea.php), go to your hosting service → **Upgrade/Downgrade** → pick Monitoring.
Site Monitoring is enabled per site. From the [client portal](https://secure.anhonesthost.com/clientarea.php), go to your hosting service → **Upgrade/Downgrade** and pick Site Monitoring.
## Where it lives in WHP
Once enabled, find it in the sidebar: **Security → AI Monitor**.
Once enabled, find it in the sidebar: **Site Monitoring**.
![AI Monitor in WHP](~/assets/screenshots/whp/whp-monitor.png)
![WHP Site Monitoring page](~/assets/screenshots/whp/whp-site-monitoring.png)
You'll see a feed of events, severity badges, and counts. Click an event for the full log context.
When the add-on isn't enabled, the page reads: *"AI monitoring is not enabled for any of your sites. Contact your hosting provider to enable this feature."*
Once enabled, the page shows a feed of events with severity badges and counts. Click an event for the full log context.
## Tuning false positives
src/content/docs/whp/add-ons/overview.mdx
+1 -1
View File
@@ -16,7 +16,7 @@ Add-ons are **optional extras** you can layer onto your base hosting plan. Each
## What's available
- **[Monitoring (AI Monitor)](/whp/add-ons/monitoring/)** — proactive alerts when something looks wrong (error spikes, brute-force attempts, exploit signatures).
- **[Site Monitoring](/whp/add-ons/monitoring/)** — proactive alerts when something looks wrong (error spikes, brute-force attempts, exploit signatures).
- **[Archival email](/whp/add-ons/archival-email/)** — long-term, searchable retention of your mail outside the live mailbox.
- **[Resource upgrades](/whp/add-ons/resource-upgrades/)** — extra CPU, RAM, or storage without changing plans.
- **[Email upgrades](/whp/add-ons/email-upgrades/)** — extra mailboxes or larger per-mailbox storage caps.
src/content/docs/whp/add-ons/resource-upgrades.mdx
+10 -13
View File
@@ -18,31 +18,28 @@ Boost your container's **CPU**, **RAM**, or **persistent disk** without migratin
Each resource is independent — upgrade only what you need.
- **CPU cores** — add cores for sustained-compute workloads.
- **RAM** — for memory-hungry apps (caches, large WordPress sites with many plugins, Node apps holding big in-memory state).
- **Persistent disk** — for sites that store a lot of files (media libraries, user uploads, backups outside our managed backup).
- **CPU cores per container** — visible on the Sites page as **CPU per Container (cores)** (default `0.25`). Add cores for sustained-compute workloads.
- **RAM per container** — visible on the Sites page as **Memory per Container (MB)** (default `256`). For memory-hungry apps (caches, large WordPress sites with many plugins, Node apps holding big in-memory state).
- **Number of containers** — scale a busy site horizontally from 1 up to 10 replicas; WHP load-balances traffic across them.
- **Persistent disk** — for sites that store a lot of files (media libraries, user uploads, etc.).
## When you might need this
- **High CPU on busy days.** Your **Overview → Resource usage** chart consistently hits the cap during peak hours.
- **"Out of memory" errors** in your app log or `dmesg`.
- **Disk usage approaching 80%** of your allocation — get ahead of it; full disks cause backup failures and uploads to fail.
- **High CPU on busy days.** Sustained-load sites consistently hit the per-container CPU cap during peak hours.
- **"Out of memory" errors** in your app log.
- **Disk usage approaching 80%** of your allocation. Get ahead of it — full disks cause backup failures and uploads to fail.
## How to enable
From the [client portal](https://secure.anhonesthost.com/clientarea.php), open your hosting service → **Upgrade/Downgrade** → pick the resource amount. WHP applies the change usually within a minute, no downtime.
For per-container CPU/RAM upgrades, edit the values directly on the **Sites** page for the site you want to change, and click **Save**. For account-wide upgrades (more total RAM, more total disk), open the [client portal](https://secure.anhonesthost.com/clientarea.php), go to your hosting service → **Upgrade/Downgrade**, and pick the resource increment.
## See your current usage
In WHP, sidebar: **Overview → Resource usage**.
![WHP Resource Usage page](~/assets/screenshots/whp/whp-resources.png)
The chart shows CPU, RAM, and disk over the last 24 hours and 7 days. If you're consistently above 80% of any line, that's the one to upgrade.
Open the **Dashboard** page in WHP. The **Server Information** and account stats show what you're consuming. For per-site usage, open a site from the **Sites** page.
## Related
- [Monitoring (AI Monitor)](/whp/add-ons/monitoring/) — catches resource saturation before customers complain.
- [Site Monitoring](/whp/add-ons/monitoring/) — catches resource saturation before customers complain.
- [Add-ons overview](/whp/add-ons/overview/)
## Still stuck?