The dashboard
Every Pressy has its own sidebar, grouped by what you are working on rather than by how difficult it is.
- Website — Overview, WordPress, Domains, Backups, Staging. The site itself.
- Server — Files, Databases, Access, PHP, Cron, Node.js, Security. The machine underneath it.
- Settings — Plan, and Cancel. Money and endings.
Every section is always visible — nothing is hidden behind an "Advanced" drawer.
Overview
The screen you land on, and the one that answers "is it fine".
- The address, copyable, plus your primary domain if one is connected.
- Visit and WordPress Admin — the second signs you into WordPress in one click, with no password to remember or store.
- Restart — restarts the container when something is wedged. It is the honest first move, and it takes seconds.
- Resource usage — memory, storage, vCPU and this month's bandwidth, each against your own plan's limit rather than a shared-account average. Refresh pulls fresh figures, throttled so the button can't be leaned on.
- Health — processes, disk IOPS, disk read and write, vCPU throttling, and out-of-memory kills. This is where "the site feels slow" turns into a number.
- Visitors and Bandwidth over 24 hours, 7 days or 30 days.
Visitor figures are counted from server requests, not sessions, so they will not match Google Analytics and the screen says so rather than letting you assume otherwise. The most recent period is still being counted and is drawn as a dashed line.
Sections that only exist in production
Domains, Plan and Cancel belong to the Pressy rather than to a copy of it, so they are production-only. Switch the dashboard into staging and they lock — and Overview becomes the staging control room instead, with the sync and push actions in place of the billing and domain cards.
The one-click sign-ins
Two buttons mint a fresh single sign-on at the moment you click, and never cache it: WordPress Admin and phpMyAdmin. You never handle a WordPress admin password or a database password to use either.
Where to go next
| You want to | Go to |
|---|---|
| Put your own domain on it | Domains |
| Try something without risking the live site | Staging |
| Get a copy of everything | Backups |
| Change memory, vCPU or storage | Plan and resources |
| Work out why it is slow | Usage and health |
Didn’t solve it?
Write to us with your Pressy’s address and what you were doing when it went wrong. Answered by the people who built it.
Last updated