Deploy And Verify

Step 0 — Parse Target

Determine what needs to be deployed from user's message:

• dle — DLE site files and/or full provision
• dle-db — database import
• dns — Cloudflare DNS records
• infra — Hetzner Cloud resources
• robots — game servers (Pelican)
• full — everything

If unclear, ask the user.

Step 1 — Pre-flight Checks

cd /Users/evgeniystepanchuk/pet-projects/AlaMine/platform/infrastructure

# Verify 1Password CLI available
op account list 2>/dev/null && echo "1Password: OK" || echo "ERROR: op CLI not authenticated. Run: eval $(op signin)"

# Verify SSH key exists
ls -la ~/.ssh/alamine_deploy && echo "Deploy key: OK"
ls -la ~/.ssh/alamine_robots && echo "Robots key: OK"

Step 2 — Terraform Phase (if infra/dns target)

# DNS changes
make tf-cf-plan
# Show plan output to user, wait for confirmation
make tf-cf-apply

# Hetzner Cloud changes
make tf-hcloud-plan
# Show plan output to user, wait for confirmation
make tf-hcloud-apply

Always show plan and wait for user confirmation before apply.

Step 3 — Ansible Phase (if dle/robots target)

DLE deploy (most common)

Required env vars on macOS (without these, deploy WILL fail):

SSH_AUTH_SOCK="" ANSIBLE_MODULE_STRICT_UTF8_RESPONSE=False make dle-deploy

Why:

• SSH_AUTH_SOCK="" — prevents Too many authentication failures from ssh-agent with multiple keys
• ANSIBLE_MODULE_STRICT_UTF8_RESPONSE=False — handles Cyrillic folder name in dle-site/

DLE full provision

SSH_AUTH_SOCK="" ANSIBLE_MODULE_STRICT_UTF8_RESPONSE=False make apply-dle

DLE DB import

# If dump path has spaces, copy first:
cp "<path with spaces>" /tmp/dump.sql
SSH_AUTH_SOCK="" ANSIBLE_MODULE_STRICT_UTF8_RESPONSE=False make dle-db-import DUMP=/tmp/dump.sql
rm /tmp/dump.sql

Robots server

make apply-robots

Step 4 — Smoke Test

After deploy completes, verify the target is working:

DLE smoke test

# Main page
curl -sI https://alamine.day | head -5
# Should return HTTP/2 200

# Admin panel
curl -sI https://alamine.day/mine.php | head -5
# Should return HTTP/2 200 or 302 (redirect to login)

# Check a known static asset
curl -sI https://alamine.day/templates/Default/style/engine.css | head -5
# Should return 200

Robots smoke test

# Pelican panel
curl -sI https://panel.alamine.day | head -5
# Should return 200 or 302

# SSH connectivity
ssh -i ~/.ssh/alamine_robots [email protected] "docker ps --format 'table {{.Names}}\t{{.Status}}'" 2>/dev/null

DNS smoke test

dig +short alamine.day
# Should return 46.225.149.38

dig +short panel.alamine.day
# Should return 65.109.56.145

Step 5 — Error Diagnosis (if smoke test fails)

# DLE server logs
ssh -i ~/.ssh/alamine_deploy [email protected] "sudo tail -50 /var/log/nginx/error.log"
ssh -i ~/.ssh/alamine_deploy [email protected] "sudo tail -50 /var/log/php8.1-fpm.log"
ssh -i ~/.ssh/alamine_deploy [email protected] "sudo systemctl status nginx php8.1-fpm mariadb memcached"

# Robots server logs
ssh -i ~/.ssh/alamine_robots [email protected] "journalctl -u wings -n 50 --no-pager"
ssh -i ~/.ssh/alamine_robots [email protected] "docker ps -a"

Common issues:

• 502 Bad Gateway — PHP-FPM not running or socket permissions wrong
• 403 Forbidden — file permissions, check chown -R www-data:www-data /var/www/dle
• 500 Internal — PHP error, check FPM log
• Connection refused — service not started, firewall blocking

Step 6 — Report

## Deploy Report

**Target:** <what was deployed>
**Commands run:** <list of make targets>
**Duration:** <approximate>

### Smoke Test Results
| URL | Status | Expected |
|-----|--------|----------|
| https://alamine.day | 200 | 200 |
| https://alamine.day/mine.php | 302 | 200/302 |

### Issues Found
<none, or list of issues with fixes applied>

### Status: OK / NEEDS ATTENTION

Constraints

• Always show Terraform plan before apply — never auto-apply
• Always use SSH_AUTH_SOCK="" for DLE deploys on macOS
• Never run make tf-*-destroy without explicit user request
• Deploy gate: show what will be deployed, wait for confirmation
• If deploy fails, diagnose — don't just retry blindly