WPHammer
Log in

Site Overview

Sites in WPHammer represent individual WordPress installations running on your synced servers. The sites list gives you a cross-server view of every WordPress site your team manages, with quick access to status, features, and configuration.

Site list

The Sites tab on the dashboard lists all WordPress sites across your servers. Each row shows:

  • Domain — the active domain with a direct link to the live site
  • Server — which server the site runs on
  • PHP version — the PHP version configured for the site
  • SSL — whether HTTPS is enabled
  • Status indicators — icons showing which features are active (backups, security, uptime, canary, inventory)

You can filter and search the site list by domain name, server, or feature status. Bulk actions let you enable or pause features across multiple sites at once.

Relationship to servers

Every site belongs to exactly one server. The server provides the runtime environment — PHP, Nginx, MySQL — and WPHammer inherits this relationship from Forge. When you view a server's detail page, you see all sites hosted on it. When you view a site, you can navigate up to its parent server.

Sites are discovered automatically during server sync. Any site created in Forge appears in WPHammer on the next sync. Sites can also be created directly from WPHammer, which provisions them through the Forge API.

Site detail page

Clicking a site name opens the detail page with tabs for:

  • Overview — domain, server, PHP version, database, WordPress version, and quick actions
  • WordPress — core version, installed plugins and themes, available updates
  • Backups — backup configuration, history, and restore options
  • Security — scan results and findings for this site
  • Uptime — monitoring status, response times, and incident history
  • Deployments — deployment history and pipeline configuration
  • Settings — site-level configuration options

Staging sites

Sites can have a staging copy linked as a child. The staging relationship is tracked via a parent ID, so WPHammer knows which production site a staging environment belongs to. This powers the push-to-production and refresh-from-production workflows.

Related