docs: migrate from torrust-demo.dev to staging-torrust-demo.com

Complete domain migration across all documentation and configuration files:

• Replace torrust-demo.dev with staging-torrust-demo.com in operational files
• Update deployment guides, DNS setup documentation, Grafana guides
• Update staging templates and deployment scripts
• Update Hetzner provider configuration guides
• Update testing documentation and manual session logs

Domain purchased: staging-torrust-demo.com (cdmon.com, Hetzner DNS)
Preserves: ADR and nginx README documentation context per user request

Fixes systematic domain references for Hetzner staging deployment
Closes #28 domain migration requirements

Author: josecelano

docs/guides/deployment-guide.md

@@ -8,19 +8,19 @@ This guide provides comprehensive deployment instructions for the Torrust Tracke
 across all supported environments:
 
 - **🏠 Local Development**: KVM/libvirt for development and testing
-- **🧪 Staging Environment**: Hetzner Cloud with `torrust-demo.dev` domain
+- **🧪 Staging Environment**: Hetzner Cloud with `staging-torrust-demo.com` domain
 - **🚀 Production Environment**: Hetzner Cloud with `torrust-demo.com` domain
 
 The deployment follows **twelve-factor app methodology** with Infrastructure as Code
 principles for reproducible, maintainable deployments.
 
 ### Deployment Environments
 
-| Environment     | Provider      | Domain             | Purpose                       | Status                   |
-| --------------- | ------------- | ------------------ | ----------------------------- | ------------------------ |
-| **Development** | KVM/libvirt   | `test.local`       | Local testing and development | ✅ **Fully Implemented** |
-| **Staging**     | Hetzner Cloud | `torrust-demo.dev` | Pre-production testing        | 🚧 **In Development**    |
-| **Production**  | Hetzner Cloud | `torrust-demo.com` | Live service                  | 🚧 **Planned**           |
+| Environment     | Provider      | Domain                     | Purpose                       | Status                   |
+| --------------- | ------------- | -------------------------- | ----------------------------- | ------------------------ |
+| **Development** | KVM/libvirt   | `test.local`               | Local testing and development | ✅ **Fully Implemented** |
+| **Staging**     | Hetzner Cloud | `staging-torrust-demo.com` | Pre-production testing        | 🚧 **In Development**    |
+| **Production**  | Hetzner Cloud | `torrust-demo.com`         | Live service                  | 🚧 **Planned**           |
 
 ## 📋 Prerequisites
 
@@ -506,7 +506,7 @@ Infrastructure: Hetzner Cloud servers with floating IPs
 
 Register your domains at any registrar. For this guide:
 
-- **Staging Domain**: `torrust-demo.dev`
+- **Staging Domain**: `staging-torrust-demo.com`
 - **Production Domain**: `torrust-demo.com`
 
 **Note**: You can use any registrar (cdmon.com, Namecheap, GoDaddy, etc.). The key is
@@ -518,7 +518,7 @@ pointing the nameservers to Hetzner DNS.
 
 1. Go to [Hetzner DNS Console](https://dns.hetzner.com/)
 2. Click **"Create zone"**
-3. Enter your domain: `torrust-demo.dev`
+3. Enter your domain: `staging-torrust-demo.com`
 4. Click **"Create zone"**
 
 Repeat for production domain: `torrust-demo.com`
@@ -537,7 +537,7 @@ After creating the zone, note the assigned nameservers:
 
 1. Log in to your cdmon.com control panel
 2. Navigate to **"Domain Management"** → **"DNS Management"**
-3. Find your domain (`torrust-demo.dev`)
+3. Find your domain (`staging-torrust-demo.com`)
 4. Click **"Modify DNS"** or **"Change Nameservers"**
 5. Replace existing nameservers with Hetzner nameservers:
    - `hydrogen.ns.hetzner.com`
@@ -558,10 +558,10 @@ The process is similar for other registrars:
 #### 4.1 Using Hetzner DNS Console
 
 1. Go to [Hetzner DNS Console](https://dns.hetzner.com/)
-2. Click on your zone (`torrust-demo.dev`)
+2. Click on your zone (`staging-torrust-demo.com`)
 3. Add the following records:
 
-**Staging Environment (`torrust-demo.dev`)**:
+**Staging Environment (`staging-torrust-demo.com`)**:
 
 | Type | Name      | Value                   | TTL |
 | ---- | --------- | ----------------------- | --- |
@@ -616,11 +616,11 @@ create_record() {
 
 # Setup staging DNS
 setup_staging_dns() {
-    echo "Setting up DNS for torrust-demo.dev..."
-    ZONE_ID=$(get_zone_id "torrust-demo.dev")
+    echo "Setting up DNS for staging-torrust-demo.com..."
+    ZONE_ID=$(get_zone_id "staging-torrust-demo.com")
 
     if [[ -z "$ZONE_ID" ]]; then
-        echo "Error: Zone not found for torrust-demo.dev"
+        echo "Error: Zone not found for staging-torrust-demo.com"
         exit 1
     fi
 
@@ -696,27 +696,27 @@ chmod +x manage-dns.sh
 
 ```bash
 # Check if nameservers have propagated
-dig NS torrust-demo.dev
+dig NS staging-torrust-demo.com
 
 # Should show Hetzner nameservers:
-# torrust-demo.dev. 3600 IN NS hydrogen.ns.hetzner.com.
-# torrust-demo.dev. 3600 IN NS oxygen.ns.hetzner.com.
-# torrust-demo.dev. 3600 IN NS helium.ns.hetzner.de.
+# staging-torrust-demo.com. 3600 IN NS hydrogen.ns.hetzner.com.
+# staging-torrust-demo.com. 3600 IN NS oxygen.ns.hetzner.com.
+# staging-torrust-demo.com. 3600 IN NS helium.ns.hetzner.de.
 ```
 
 #### 5.2 Test DNS Resolution
 
 ```bash
 # Test staging domain resolution
-dig tracker.torrust-demo.dev
-dig AAAA tracker.torrust-demo.dev
+dig tracker.staging-torrust-demo.com
+dig AAAA tracker.staging-torrust-demo.com
 
 # Test production domain resolution
 dig tracker.torrust-demo.com
 dig AAAA tracker.torrust-demo.com
 
 # Verify the records point to your floating IPs
-nslookup tracker.torrust-demo.dev
+nslookup tracker.staging-torrust-demo.com
 nslookup tracker.torrust-demo.com
 ```
 
@@ -729,7 +729,7 @@ Use online tools to verify global propagation:
 
 Search for:
 
-- `tracker.torrust-demo.dev` (A record)
+- `tracker.staging-torrust-demo.com` (A record)
 - `tracker.torrust-demo.com` (A record)
 
 ### Step 6: DNS Management Scripts
@@ -743,7 +743,7 @@ For ongoing DNS management, create utility scripts:
 # list-dns-records.sh
 
 HDNS_TOKEN="your-hetzner-dns-token"
-DOMAIN=${1:-"torrust-demo.dev"}
+DOMAIN=${1:-"staging-torrust-demo.com"}
 
 # Get zone ID
 ZONE_ID=$(curl -s -H "Auth-API-Token: $HDNS_TOKEN" \
@@ -772,7 +772,7 @@ curl -s -H "Auth-API-Token: $HDNS_TOKEN" \
 # update-dns-record.sh
 
 HDNS_TOKEN="your-hetzner-dns-token"
-DOMAIN="torrust-demo.dev"
+DOMAIN="staging-torrust-demo.com"
 SUBDOMAIN="tracker"
 NEW_IP="78.47.140.132"
 
@@ -815,8 +815,8 @@ automatic subdomain concatenation. Configure each service domain separately.
 When you configure:
 
 ```bash
-TRACKER_DOMAIN=tracker.torrust-demo.dev
-GRAFANA_DOMAIN=grafana.torrust-demo.dev
+TRACKER_DOMAIN=tracker.staging-torrust-demo.com
+GRAFANA_DOMAIN=grafana.staging-torrust-demo.com
 ```
 
 The system uses these exact domain names:
@@ -827,8 +827,8 @@ The system uses these exact domain names:
 #### Required Domain Configuration
 
 - **Staging**:
-  - `TRACKER_DOMAIN=tracker.torrust-demo.dev`
-  - `GRAFANA_DOMAIN=grafana.torrust-demo.dev`
+  - `TRACKER_DOMAIN=tracker.staging-torrust-demo.com`
+  - `GRAFANA_DOMAIN=grafana.staging-torrust-demo.com`
 - **Production**:
   - `TRACKER_DOMAIN=tracker.torrust-demo.com`
   - `GRAFANA_DOMAIN=grafana.torrust-demo.com`
@@ -975,21 +975,21 @@ HCLOUD_FLOATING_IPV6=2a01:4f8:1c17:a01d::1
 
 # === HETZNER DNS CONFIGURATION ===
 HDNS_TOKEN=your-hetzner-dns-token
-HDNS_ZONE_NAME=torrust-demo.dev
+HDNS_ZONE_NAME=staging-torrust-demo.com
 
 # === VM CONFIGURATION ===
 VM_TYPE=cx22  # 4 vCPU, 8GB RAM, 80GB SSD
 VM_LOCATION=nbg1  # Nuremberg
 VM_IMAGE=ubuntu-24.04
 
 # === DOMAIN CONFIGURATION ===
-TRACKER_DOMAIN=tracker.torrust-demo.dev
-GRAFANA_DOMAIN=grafana.torrust-demo.dev
+TRACKER_DOMAIN=tracker.staging-torrust-demo.com
+GRAFANA_DOMAIN=grafana.staging-torrust-demo.com
 
 # === SSL CONFIGURATION ===
 ENABLE_SSL=true
 SSL_GENERATION_METHOD=letsencrypt
-CERTBOT_EMAIL=admin@torrust-demo.dev
+CERTBOT_EMAIL=admin@staging-torrust-demo.com
 
 # === DATABASE CONFIGURATION ===
 MYSQL_ROOT_PASSWORD=secure_staging_root_password
@@ -1138,11 +1138,11 @@ make app-health-check ENVIRONMENT_TYPE=staging
 
 ```bash
 # Test staging endpoints
-curl -s https://tracker.torrust-demo.dev/api/health_check | jq
-curl -s "https://tracker.torrust-demo.dev/api/v1/stats?token=$ADMIN_TOKEN" | jq
+curl -s https://tracker.staging-torrust-demo.com/api/health_check | jq
+curl -s "https://tracker.staging-torrust-demo.com/api/v1/stats?token=$ADMIN_TOKEN" | jq
 
 # Monitor staging
-open https://grafana.torrust-demo.dev
+open https://grafana.staging-torrust-demo.com
 ```
 
 ### Production Workflow (Coming Soon)
@@ -1194,14 +1194,14 @@ ssh [email protected] \
 
 #### Cloud Services
 
-| Service           | Staging URL                                                 | Production URL                                              | Purpose      |
-| ----------------- | ----------------------------------------------------------- | ----------------------------------------------------------- | ------------ |
-| **Tracker API**   | `https://tracker.torrust-demo.dev/api/health_check`         | `https://tracker.torrust-demo.com/api/health_check`         | Health check |
-| **Tracker Stats** | `https://tracker.torrust-demo.dev/api/v1/stats?token=TOKEN` | `https://tracker.torrust-demo.com/api/v1/stats?token=TOKEN` | Statistics   |
-| **HTTP Tracker**  | `https://tracker.torrust-demo.dev/announce`                 | `https://tracker.torrust-demo.com/announce`                 | HTTP tracker |
-| **UDP Tracker**   | `udp://tracker.torrust-demo.dev:6868/announce`              | `udp://tracker.torrust-demo.com:6868/announce`              | UDP tracker  |
-| **UDP Tracker**   | `udp://tracker.torrust-demo.dev:6969/announce`              | `udp://tracker.torrust-demo.com:6969/announce`              | UDP tracker  |
-| **Grafana**       | `https://grafana.torrust-demo.dev`                          | `https://grafana.torrust-demo.com`                          | Monitoring   |
+| Service           | Staging URL                                                         | Production URL                                              | Purpose      |
+| ----------------- | ------------------------------------------------------------------- | ----------------------------------------------------------- | ------------ |
+| **Tracker API**   | `https://tracker.staging-torrust-demo.com/api/health_check`         | `https://tracker.torrust-demo.com/api/health_check`         | Health check |
+| **Tracker Stats** | `https://tracker.staging-torrust-demo.com/api/v1/stats?token=TOKEN` | `https://tracker.torrust-demo.com/api/v1/stats?token=TOKEN` | Statistics   |
+| **HTTP Tracker**  | `https://tracker.staging-torrust-demo.com/announce`                 | `https://tracker.torrust-demo.com/announce`                 | HTTP tracker |
+| **UDP Tracker**   | `udp://tracker.staging-torrust-demo.com:6868/announce`              | `udp://tracker.torrust-demo.com:6868/announce`              | UDP tracker  |
+| **UDP Tracker**   | `udp://tracker.staging-torrust-demo.com:6969/announce`              | `udp://tracker.torrust-demo.com:6969/announce`              | UDP tracker  |
+| **Grafana**       | `https://grafana.staging-torrust-demo.com`                          | `https://grafana.torrust-demo.com`                          | Monitoring   |
 
 ### Service Management Commands
 
@@ -1299,7 +1299,7 @@ curl -I https://tracker.torrust-demo.com
 
 **⚠️ Important**: Grafana requires manual setup after deployment.
 
-1. **Access Grafana**: `https://grafana.torrust-demo.dev` (or production URL)
+1. **Access Grafana**: `https://grafana.staging-torrust-demo.com` (or production URL)
 2. **Login**: `admin/admin` (change password immediately)
 3. **Add Prometheus data source**: `http://prometheus:9090`
 4. **Import dashboards** from `application/share/grafana/dashboards/`
@@ -1414,11 +1414,11 @@ systemctl status ufw
 
    ```bash
    # Check nameserver propagation
-   dig NS torrust-demo.dev
+   dig NS staging-torrust-demo.com
 
    # Test DNS resolution
-   dig tracker.torrust-demo.dev
-   nslookup tracker.torrust-demo.dev
+   dig tracker.staging-torrust-demo.com
+   nslookup tracker.staging-torrust-demo.com
 
    # Check global propagation
    # Use whatsmydns.net or dnschecker.org