Server Overview
WPHammer organizes everything around the servers synced from your Laravel Forge account. The servers list is the starting point for understanding your infrastructure — which servers are active, what they are running, and whether they need attention.
Server list
The Servers tab on the dashboard shows all synced servers in your team. Each server row displays:
- Name — the server name as configured in Forge
- IP address — the public IPv4 address
- Provider — the hosting provider (DigitalOcean, AWS, Hetzner, etc.)
- Region — the data center region where the server is provisioned
- PHP version — the active PHP version on the server
- Disk usage — percentage of disk space used, collected via SSH health checks
Click any server name to open its detail page, where you can review sites, health metrics, and configuration.
Status indicators
Servers show status based on several signals:
Readiness
A server is considered ready when it has been fully provisioned in Forge and WPHammer can communicate with it. Servers that are still provisioning or have lost connectivity show as not ready.
Service availability
WPHammer tracks whether key services are running:
- Nginx — the web server handling HTTP traffic
- MySQL — the database server for WordPress sites
If either service is reported as inactive, the server detail page highlights this so you can investigate.
Onboarding status
New servers go through an onboarding process that verifies:
- Firewall configuration allows WPHammer access
- Sudo access is available for administrative commands
- WP-CLI is installed and functional
Servers that have not completed onboarding show a setup indicator. Complete onboarding to unlock full management features like health checks, security scanning, and backup configuration.
Forge sync relationship
Servers in WPHammer are mirrors of your Forge servers. WPHammer does not provision or destroy servers — it reads server data from the Forge API and stores a local working copy.
Key points about the sync relationship:
- Server identity is linked by Forge ID. Renaming a server in Forge updates it in WPHammer on the next sync.
- Sites on each server are discovered automatically during sync. Any site created in Forge appears in WPHammer after syncing.
- Changes in Forge (new servers, removed servers, configuration changes) are reflected in WPHammer when you sync — either manually or on schedule.
- Tag filtering limits which servers sync based on Forge tags configured in your team settings.
WPHammer adds its own data on top of Forge — health metrics, security findings, backup history, and monitoring — but the underlying server and site records originate from Forge.
Server detail page
The server detail page provides a deeper view with tabs for:
- Overview — server metadata, onboarding status, and quick actions
- Sites — all WordPress sites on this server
- Health — CPU, memory, disk, and service metrics
- Security — security scan results and findings
- Backups — backup configurations and history for sites on this server
Related
- Server Health — Health metrics and monitoring
- Disk Usage — Storage monitoring and thresholds
- Server Security — Security scanning overview
- Syncing Servers — How server data flows from Forge