Merge pull request #73 from imagewize/generic-user-and-site

Generic User And Site

Author: jasperf

CHANGELOG.md

@@ -7,6 +7,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.3.1] - 2026-01-01
+
+### Changed
+
+- **Standardized placeholder domain across documentation** - Replaced `imagewize.com` with `example.com` for consistency in all generic examples and documentation:
+  - Updated 13 files across scripts, documentation, and configuration examples
+  - Affected files: PAGE-CREATION.md, MULTI-SITE-MIGRATION.md, CRON.md, PROJECT-SETUP.md, nginx/README.md, nginx/redirects/README.md, scripts/README.md, monitoring scripts, and more
+  - Preserved historical references to `imagewize.com` in CHANGELOG.md to maintain accurate project history
+  - Preserved real-world production data and case studies in security documentation (FAIL2BAN.md, security/README.md, MANUAL-IP-BLOCKING.md) which contain actual attack statistics and production examples
+  - Enhanced documentation clarity by using industry-standard `example.com` placeholder domain (RFC 2606)
+
 ## [2.3.0] - 2026-01-01
 
 ### Added

nginx/README.md

@@ -197,7 +197,7 @@ SEO-friendly redirect templates for URL migrations, permalink changes, and canon
 - `wordpress-permalinks.conf.j2` - Common permalink migration patterns
 
 **Real-world example:**
-- `imagewize.com/seo-redirects.conf.j2` - Production redirect patterns
+- `example.com/seo-redirects.conf.j2` - Production redirect patterns
 
 ### Configuration Examples
 

nginx/redirects/README.md

@@ -12,7 +12,7 @@ This directory contains example nginx redirect configurations that can be used i
 redirects/
 ├── README.md                           # This file
 └── examples/
-    ├── imagewize.com/
+    ├── example.com/
     │   └── seo-redirects.conf.j2       # SEO redirect examples
     └── generic/
         ├── wordpress-permalinks.conf.j2 # Common WordPress redirects
@@ -35,8 +35,8 @@ trellis/
 └── nginx-includes/
     ├── all/                          # Global includes (all sites)
     │   └── assets-expiry.conf.j2     # Browser caching rules
-    └── imagewize.com/                # Site-specific includes
-        └── seo-redirects.conf.j2     # SEO redirects (imagewize.com only)
+    └── example.com/                # Site-specific includes
+        └── seo-redirects.conf.j2     # SEO redirects (example.com only)
 ```
 
 ### Deployment Location
@@ -47,8 +47,8 @@ Templates are deployed to `/etc/nginx/includes.d/` on the server:
 /etc/nginx/includes.d/
 ├── all/
 │   └── assets-expiry.conf         # Rendered from all/assets-expiry.conf.j2
-└── imagewize.com/
-    └── seo-redirects.conf         # Rendered from imagewize.com/seo-redirects.conf.j2
+└── example.com/
+    └── seo-redirects.conf         # Rendered from example.com/seo-redirects.conf.j2
 ```
 
 ## Using the Examples
@@ -57,7 +57,7 @@ Templates are deployed to `/etc/nginx/includes.d/` on the server:
 
 ```bash
 # Copy site-specific redirect template
-cp ~/code/trellis-tools/redirects/examples/imagewize.com/seo-redirects.conf.j2 \
+cp ~/code/trellis-tools/redirects/examples/example.com/seo-redirects.conf.j2 \
    ~/code/yourproject.com/trellis/nginx-includes/yoursite.com/
 
 # Or copy to global includes (applies to all sites)

scripts/README.md

@@ -213,8 +213,8 @@ Edit script to set theme paths:
 
 ```bash
 # Bedrock installation directories
-DEMO_DIR="$HOME/code/imagewize.com/demo/web/app/themes"
-SITE_DIR="$HOME/code/imagewize.com/site/web/app/themes"
+DEMO_DIR="$HOME/code/example.com/demo/web/app/themes"
+SITE_DIR="$HOME/code/example.com/site/web/app/themes"
 ```
 
 #### Example Changelog Output
@@ -278,7 +278,7 @@ Simple rsync wrapper for theme synchronization between Trellis and standalone re
 Edit script with your paths:
 
 ```bash
-SOURCE="$HOME/code/imagewize.com/demo/web/app/themes/elayne/"
+SOURCE="$HOME/code/example.com/demo/web/app/themes/elayne/"
 DESTINATION="$HOME/code/elayne/"
 ```
 
@@ -503,7 +503,7 @@ Real-time Nginx traffic analysis with intelligent bot filtering and comprehensiv
 ./traffic-monitor.sh
 
 # Specific log file and time window
-./traffic-monitor.sh /srv/www/demo.imagewize.com/logs/access.log 6
+./traffic-monitor.sh /srv/www/demo.example.com/logs/access.log 6
 
 # Last 24 hours
 ./traffic-monitor.sh /var/log/nginx/access.log 24

scripts/monitoring/security-monitor.sh

@@ -6,8 +6,8 @@
 #   ./security-monitor.sh [log_file] [hours] [alert_threshold]
 #
 # Examples:
-#   ./security-monitor.sh                                                # Default: imagewize.com, last 24h
-#   ./security-monitor.sh /srv/www/demo.imagewize.com/logs/access.log 1 50     # Demo site, 1 hour, alert > 50
+#   ./security-monitor.sh                                                # Default: example.com, last 24h
+#   ./security-monitor.sh /srv/www/demo.example.com/logs/access.log 1 50     # Demo site, 1 hour, alert > 50
 #   ./security-monitor.sh /var/log/nginx/access.log 24 100                     # Global logs, 24h, alert > 100
 #
 
@@ -19,11 +19,11 @@ set -e
 
 # Default log file - adjust to your site:
 # Per-site logs (Trellis default):
-#   /srv/www/imagewize.com/logs/access.log
-#   /srv/www/demo.imagewize.com/logs/access.log
+#   /srv/www/example.com/logs/access.log
+#   /srv/www/demo.example.com/logs/access.log
 # Global logs (if configured):
 #   /var/log/nginx/access.log
-LOG_FILE="${1:-/srv/www/imagewize.com/logs/access.log}"
+LOG_FILE="${1:-/srv/www/example.com/logs/access.log}"
 HOURS="${2:-24}"
 ALERT_THRESHOLD="${3:-100}"  # Alert if single IP exceeds this many requests
 

scripts/monitoring/traffic-monitor.sh

@@ -6,8 +6,8 @@
 #   ./traffic-monitor.sh [log_file] [hours]
 #
 # Examples:
-#   ./traffic-monitor.sh                                           # Default: imagewize.com, last 24h
-#   ./traffic-monitor.sh /srv/www/demo.imagewize.com/logs/access.log 6  # Demo site, last 6 hours
+#   ./traffic-monitor.sh                                           # Default: example.com, last 24h
+#   ./traffic-monitor.sh /srv/www/demo.example.com/logs/access.log 6  # Demo site, last 6 hours
 #   ./traffic-monitor.sh /var/log/nginx/access.log 24             # Global logs, last 24 hours
 #
 
@@ -19,11 +19,11 @@ set -e
 
 # Default log file - adjust to your site:
 # Per-site logs (Trellis default):
-#   /srv/www/imagewize.com/logs/access.log
-#   /srv/www/demo.imagewize.com/logs/access.log
+#   /srv/www/example.com/logs/access.log
+#   /srv/www/demo.example.com/logs/access.log
 # Global logs (if configured):
 #   /var/log/nginx/access.log
-LOG_FILE="${1:-/srv/www/imagewize.com/logs/access.log}"
+LOG_FILE="${1:-/srv/www/example.com/logs/access.log}"
 HOURS="${2:-24}"
 
 # Bot patterns to exclude from traffic analysis

scripts/rsync-theme.sh

@@ -23,6 +23,6 @@ rsync -av --delete \
   --exclude 'vendor/' \
   --exclude '.git/' \
   --exclude '.github/' \
-  ~/code/imagewize.com/demo/web/app/themes/elayne/ \
+  ~/code/example.com/demo/web/app/themes/elayne/ \
   ~/code/elayne/
 

trellis/provision/CRON.md

@@ -37,8 +37,8 @@ This sets `DISABLE_WP_CRON` constant to `true` in WordPress configuration.
 
 ```bash
 # Example: /etc/cron.d/wordpress-imagewize_com
-#Ansible: imagewize.com WordPress cron
-*/15 * * * * web cd /srv/www/imagewize.com/current && wp cron event run --due-now > /dev/null 2>&1
+#Ansible: example.com WordPress cron
+*/15 * * * * web cd /srv/www/example.com/current && wp cron event run --due-now > /dev/null 2>&1
 ```
 
 **What this does:**
@@ -54,8 +54,8 @@ For **WordPress multisite** installations, the cron configuration is different t
 
 ```bash
 # Example: /etc/cron.d/wordpress-demo_imagewize_com
-#Ansible: demo.imagewize.com WordPress cron
-*/15 * * * * web cd /srv/www/demo.imagewize.com/current && (wp site list --field=url | xargs -n1 -I % wp --url=% cron event run --due-now) > /dev/null 2>&1
+#Ansible: demo.example.com WordPress cron
+*/15 * * * * web cd /srv/www/demo.example.com/current && (wp site list --field=url | xargs -n1 -I % wp --url=% cron event run --due-now) > /dev/null 2>&1
 ```
 
 **What this does:**
@@ -66,7 +66,7 @@ For **WordPress multisite** installations, the cron configuration is different t
 **Multisite cron log example:**
 
 ```
-2025-11-28T02:30:01 ubuntu CRON[93961]: (web) CMD (cd /srv/www/demo.imagewize.com/current && (wp site list --field=url | xargs -n1 -I % wp --url=% cron event run --due-now) > /dev/null 2>&1)
+2025-11-28T02:30:01 ubuntu CRON[93961]: (web) CMD (cd /srv/www/demo.example.com/current && (wp site list --field=url | xargs -n1 -I % wp --url=% cron event run --due-now) > /dev/null 2>&1)
 ```
 
 ## Verification
@@ -112,9 +112,9 @@ sudo -u web bash -c "cd /srv/www/example.com/current && wp cron event run --due-
 **Example of successful cron execution in logs:**
 
 ```
-2025-11-28T02:15:01 ubuntu CRON[93164]: (web) CMD (cd /srv/www/imagewize.com/current && wp cron event run --due-now > /dev/null 2>&1)
-2025-11-28T02:30:01 ubuntu CRON[93960]: (web) CMD (cd /srv/www/imagewize.com/current && wp cron event run --due-now > /dev/null 2>&1)
-2025-11-28T02:45:01 ubuntu CRON[94288]: (web) CMD (cd /srv/www/imagewize.com/current && wp cron event run --due-now > /dev/null 2>&1)
+2025-11-28T02:15:01 ubuntu CRON[93164]: (web) CMD (cd /srv/www/example.com/current && wp cron event run --due-now > /dev/null 2>&1)
+2025-11-28T02:30:01 ubuntu CRON[93960]: (web) CMD (cd /srv/www/example.com/current && wp cron event run --due-now > /dev/null 2>&1)
+2025-11-28T02:45:01 ubuntu CRON[94288]: (web) CMD (cd /srv/www/example.com/current && wp cron event run --due-now > /dev/null 2>&1)
 ```
 
 If you see entries like these running every 15 minutes, your WordPress cron is working correctly.
@@ -123,7 +123,7 @@ If you see entries like these running every 15 minutes, your WordPress cron is w
 
 ```bash
 # Check only cron logs for a specific site
-sudo grep -i cron /var/log/syslog | grep "imagewize.com" | tail -20
+sudo grep -i cron /var/log/syslog | grep "example.com" | tail -20
 
 # Check cron logs for all sites
 sudo grep -i cron /var/log/syslog | grep "(web) CMD" | tail -20

trellis/provision/PROJECT-SETUP.md

@@ -193,7 +193,7 @@ If you're setting up an existing project on a new machine, copy the `.vault_pass
 cat /path/to/project/trellis/.vault_pass
 
 # On your new machine
-cd /Users/j/code/imagewize.com/trellis
+cd /Users/j/code/example.com/trellis
 echo "PASTE_PASSWORD_HERE" > .vault_pass
 chmod 600 .vault_pass
 ```