Skip to content

v2.0.4 - Configuration Blueprints & Enhanced Export

Choose a tag to compare

@pimschaaf pimschaaf released this 30 Oct 08:46
· 3 commits to main since this release

v2.0.4 - Configuration Blueprints & Enhanced Export

🎯 What's New

Configuration Blueprints

Export only the settings this plugin can manage - perfect for creating reusable security configuration templates!

# Create a security baseline blueprint (~42 managed settings)
wp wf-config export /tmp/security-blueprint.json --managed-only

# vs. full export (all 280+ Wordfence settings including internal state)
wp wf-config export /tmp/full-audit.json

Why Use Blueprints?

Full Export (wp wf-config export):

  • All 280+ Wordfence settings
  • Includes internal state, counters, timestamps
  • Best for: Complete audits, full backups, troubleshooting

Blueprint Export (wp wf-config export --managed-only):

  • Only ~42 manageable settings (security policies)
  • Clean, focused configuration
  • Best for: Site migrations, standardization, version control

✨ Features

New --managed-only Flag

  • Export only settings that can be managed by this plugin's commands
  • Includes: brute force protection, firewall, scanner, and alert settings
  • Excludes: internal state, API keys, transient data

Enhanced Export Functionality

  • ✅ Better error handling with JSON encoding validation
  • ✅ Binary blob (LONGBLOB) data support
  • ✅ Shows bytes written confirmation
  • ✅ Handles invalid UTF-8 characters gracefully
  • ✅ Detailed error messages for troubleshooting

🚀 Use Cases

1. Site Migrations

# Export from production
wp wf-config export /tmp/prod-security.json --managed-only

# Apply to staging
wp wf-config import /tmp/prod-security.json --url=staging.com --backup

2. Standardized Deployments

# Create your security baseline once
wp wf-config export /tmp/baseline.json --managed-only

# Deploy to multiple sites
for site in site1.com site2.com site3.com; do
  wp wf-config import /tmp/baseline.json --url=$site --force
done

3. Version Control

# Store your security policies in git
wp wf-config export config/wordfence-baseline.json --managed-only
git add config/wordfence-baseline.json
git commit -m "Update security baseline: increase lockout duration"

4. Audits & Compliance

# Smaller, focused export makes auditing easier
wp wf-config export /tmp/audit-$(date +%Y%m%d).json --managed-only

# Review only the settings that matter for compliance
cat /tmp/audit-20251030.json | jq '.settings'

🔧 Settings Included in Blueprints

Blueprints include 42 manageable settings:

  • Brute Force (10): Login security, max failures, lockout duration
  • Firewall (3): Firewall enabled, auto-block settings
  • Scanner (12): Scan types, sensitivity, limits
  • Alerts (9): Email addresses, alert triggers

Full list available in the documentation.

📚 Documentation Updates

  • Added "Configuration Blueprints & Site Migrations" section
  • Updated all command examples
  • Added comparison table: Full vs Blueprint exports
  • Comprehensive use case examples

Full Changelog: v2.0.3...v2.0.4