docs: update references from hetzner.env to hetzner-staging.env

Updates all documentation to reflect the provider configuration file rename:
- Testing documentation: manual deployment and session guides
- Scripts: manage-hetzner-dns.sh with staging-specific provider config
- Template: hetzner.env.tpl with updated instructions
- README: provider configuration documentation
- Deployment guides: staging-specific references

This maintains consistency between actual file naming and documentation
for Issue #28 Phase 4.7 staging deployment testing.

Author: josecelano

docs/guides/deployment-guide.md

@@ -94,7 +94,7 @@ make infra-destroy
 
 ```bash
 # Configure Hetzner provider with your API tokens first
-vim infrastructure/config/providers/hetzner.env
+vim infrastructure/config/providers/hetzner-staging.env
 
 # Generate staging environment configuration
 make infra-config-staging PROVIDER=hetzner
@@ -893,7 +893,7 @@ TRACKER_ADMIN_TOKEN=MyAccessToken
 The deployment system uses a **two-file architecture** for maximum security and flexibility:
 
 1. **Environment Files**: Environment-specific settings (staging-hetzner.env, production-hetzner.env)
-2. **Provider Files**: API tokens and provider configuration (hetzner.env)
+2. **Provider Files**: API tokens and provider configuration (hetzner-staging.env)
 
 **Benefits**:
 
@@ -912,7 +912,7 @@ Before creating environment configurations, you must configure the Hetzner provi
 
 ```bash
 # Edit the Hetzner provider configuration
-vim infrastructure/config/providers/hetzner.env
+vim infrastructure/config/providers/hetzner-staging.env
 ```
 
 **Required Changes**:

docs/guides/staging-deployment-testing-guide.md

@@ -44,7 +44,7 @@ make install-deps
 make lint
 
 # Check provider configuration
-cat infrastructure/config/providers/hetzner.env
+cat infrastructure/config/providers/hetzner-staging.env
 
 # Verify environment templates exist
 ls infrastructure/config/environments/staging-hetzner.env.tpl
@@ -55,7 +55,7 @@ ls infrastructure/config/environments/staging-hetzner.env.tpl
 Ensure these are configured in your provider configuration:
 
 ```bash
-# From infrastructure/config/providers/hetzner.env
+# From infrastructure/config/providers/hetzner-staging.env
 HETZNER_API_TOKEN=your-cloud-api-token
 HETZNER_DNS_API_TOKEN=your-dns-api-token
 ```

docs/issues/28-phase-4-hetzner-infrastructure-implementation.md

@@ -117,7 +117,7 @@ production-ready cloud deployment system.
 
 **Key Files Created**:
 
-- `infrastructure/config/providers/hetzner.env` - Secure API token storage
+- `infrastructure/config/providers/hetzner-staging.env` - Secure API token storage
 - `docs/guides/providers/hetzner/hetzner-cloud-setup-guide.md` - Complete setup guide
 - Environment templates in `infrastructure/config/environments/`
 
@@ -511,7 +511,7 @@ to Hetzner DNS servers before infrastructure deployment can proceed.
 
 ### API Token Management
 
-- **Storage**: `infrastructure/config/providers/hetzner.env` (git-ignored)
+- **Storage**: `infrastructure/config/providers/hetzner-staging.env` (git-ignored)
 - **Cloud Token**: 64 characters, Read & Write permissions
 - **DNS Token**: 32 characters, Zone:Edit permissions
 - **Validation**: Both tokens tested and working
@@ -525,7 +525,7 @@ to Hetzner DNS servers before infrastructure deployment can proceed.
 
 ```bash
 # Always source the provider configuration first
-source infrastructure/config/providers/hetzner.env
+source infrastructure/config/providers/hetzner-staging.env
 
 # Then use the correct variable names
 curl -H "Authorization: Bearer $HETZNER_API_TOKEN" https://api.hetzner.cloud/v1/...
@@ -579,7 +579,7 @@ The Hetzner implementation builds on the existing twelve-factor architecture:
 ### File System Integration
 
 ```text
-✅ infrastructure/config/providers/hetzner.env - API tokens
+✅ infrastructure/config/providers/hetzner-staging.env - API tokens
 ✅ infrastructure/config/environments/ - Environment templates
 ✅ docs/guides/providers/hetzner/ - Provider documentation
 📝 infrastructure/terraform/providers/hetzner/ - Terraform modules

docs/testing/manual-sessions/2025-01-08-issue-28-phase-4-7-staging.md

@@ -47,7 +47,7 @@ workflow using real Hetzner Cloud infrastructure with the torrust-demo.dev domai
 **Configuration Files**:
 
 - **Environment File**: `infrastructure/config/environments/staging-hetzner.env`
-- **Provider File**: `infrastructure/config/providers/hetzner.env`
+- **Provider File**: `infrastructure/config/providers/hetzner-staging.env`
 - **Templates**: All staging templates validated
 
 **Prerequisites Required**:
@@ -83,7 +83,7 @@ workflow using real Hetzner Cloud infrastructure with the torrust-demo.dev domai
 
 ```bash
 # 1. Verify provider configuration
-cat infrastructure/config/providers/hetzner.env
+cat infrastructure/config/providers/hetzner-staging.env
 
 # 2. Validate environment configuration
 make infra-config-validate ENVIRONMENT_TYPE=staging ENVIRONMENT_FILE=staging-hetzner
@@ -383,7 +383,7 @@ Upon successful completion of Phase 4.7, the project will be ready for:
 
 ### Immediate Actions Required
 
-- [ ] Configure provider tokens in `infrastructure/config/providers/hetzner.env`
+- [ ] Configure provider tokens in `infrastructure/config/providers/hetzner-staging.env`
 - [ ] Validate DNS zone configuration for torrust-demo.dev
 - [ ] Ensure SSH key is properly configured
 - [ ] Begin Phase 1: Environment Preparation

docs/testing/manual-staging-deployment-testing.md

@@ -29,7 +29,7 @@ virtualization, staging testing provides:
 ### Configuration Files
 
 - `infrastructure/config/environments/staging-hetzner.env`
-- `infrastructure/config/providers/hetzner.env`
+- `infrastructure/config/providers/hetzner-staging.env`
 
 ### Validation Commands
 
@@ -38,7 +38,7 @@ virtualization, staging testing provides:
 ls -la infrastructure/config/environments/staging-hetzner.env
 
 # Check provider configuration
-ls -la infrastructure/config/providers/hetzner.env
+ls -la infrastructure/config/providers/hetzner-staging.env
 
 # Validate configuration syntax
 make infra-config-validate ENVIRONMENT_TYPE=staging ENVIRONMENT_FILE=staging-hetzner

infrastructure/config/providers/README.md

@@ -28,7 +28,7 @@ infrastructure/config/templates/providers/
 ### Hetzner Cloud Provider (Production)
 
 - **Template**: `infrastructure/config/templates/providers/hetzner.env.tpl`
-- **User File**: `hetzner.env` (create from template)
+- **User File**: `hetzner-staging.env` (create from template)
 - **Purpose**: Hetzner Cloud deployment for production environments
 
 ## Usage Instructions
@@ -54,7 +54,7 @@ can override provider defaults:
 #### Example Scenario
 
 ```bash
-# Provider config (hetzner.env) - defaults for ALL environments
+# Provider config (hetzner-staging.env) - defaults for ALL environments
 HETZNER_SERVER_TYPE=cpx31      # Default: 4 vCPU, 8GB RAM
 HETZNER_LOCATION=fsn1          # Default: Falkenstein datacenter
 
@@ -72,7 +72,7 @@ HETZNER_LOCATION=fsn1          # Default: Falkenstein datacenter
    cp infrastructure/config/templates/providers/libvirt.env.tpl infrastructure/config/providers/libvirt.env
 
    # For Hetzner Cloud
-   cp infrastructure/config/templates/providers/hetzner.env.tpl infrastructure/config/providers/hetzner.env
+   cp infrastructure/config/templates/providers/hetzner.env.tpl infrastructure/config/providers/hetzner-staging.env
    ```
 
 2. **Edit the copied file** with your actual values:

infrastructure/config/templates/providers/hetzner.env.tpl

@@ -1,6 +1,6 @@
 # Hetzner Cloud Provider Configuration Template
-# Copy this file to hetzner.env and replace placeholder values
-# Location: infrastructure/config/providers/hetzner.env
+# Copy this file to hetzner-staging.env and replace placeholder values
+# Location: infrastructure/config/providers/hetzner-staging.env
 
 # === HETZNER CLOUD AUTHENTICATION ===
 # Get your API token from: https://console.hetzner.cloud/

infrastructure/docs/configuration-architecture.md

@@ -21,7 +21,7 @@ and providers (libvirt, Hetzner Cloud).
 
 **Location**: `infrastructure/config/providers/`  
 **Purpose**: Provider-wide defaults and authentication  
-**Examples**: `libvirt.env`, `hetzner.env`
+**Examples**: `libvirt.env`, `hetzner-staging.env`
 
 ## Loading Order and Override System
 
@@ -32,7 +32,7 @@ During deployment, configurations are loaded in this specific order:
 source "infrastructure/config/environments/production-hetzner.env"
 
 # 2. Provider configuration loaded second (can override environment values)
-source "infrastructure/config/providers/hetzner.env"
+source "infrastructure/config/providers/hetzner-staging.env"
 ```
 
 ### Why This Order?

project-words.txt

@@ -77,6 +77,7 @@ newtrackon
 nmap
 noatime
 NONCEREJECT
+noout
 NOPASSWD
 NOSLEEP
 nosniff
@@ -108,6 +109,7 @@ SAMEORIGIN
 secp
 selfsigned
 shellcheck
+showcerts
 somaxconn
 sshpass
 Taplo

scripts/manage-hetzner-dns.sh

@@ -61,13 +61,13 @@ load_token() {
     log_info "Loading Hetzner DNS API token from provider configuration..."
 
     # Load provider configuration
-    local provider_config="${PROJECT_ROOT}/infrastructure/config/providers/hetzner.env"
+    local provider_config="${PROJECT_ROOT}/infrastructure/config/providers/hetzner-staging.env"
 
     if [[ ! -f "$provider_config" ]]; then
         log_error "Provider configuration not found at: $provider_config"
         log_error ""
         log_error "Please create the configuration file from template:"
-        log_error "  cp infrastructure/config/templates/providers/hetzner.env.tpl infrastructure/config/providers/hetzner.env"
+        log_error "  cp infrastructure/config/templates/providers/hetzner.env.tpl infrastructure/config/providers/hetzner-staging.env"
         log_error "  # Edit the file and set HETZNER_DNS_API_TOKEN"
         exit 1
     fi
@@ -331,11 +331,11 @@ Examples:
   $0 check-propagation grafana
 
 Prerequisites:
-  - API token configured in infrastructure/config/providers/hetzner.env
+  - API token configured in infrastructure/config/providers/hetzner-staging.env
   - curl and jq installed
 
 Setup:
-  1. Copy template: cp infrastructure/config/templates/providers/hetzner.env.tpl infrastructure/config/providers/hetzner.env
+  1. Copy template: cp infrastructure/config/templates/providers/hetzner.env.tpl infrastructure/config/providers/hetzner-staging.env
   2. Edit file and set: HETZNER_DNS_API_TOKEN=your_dns_api_token_here
   3. Get token from: https://dns.hetzner.com/