Files
aitbc/scripts/deploy/.env.deploy.example
AITBC System 42422500c1 fix: remove hardcoded passwords and enhance security in production setup
Security Enhancements:
- Update .gitignore header timestamp to 2026-03-18 for security fixes
- Add CRITICAL SECURITY markers to sensitive sections in .gitignore
- Add comprehensive password file patterns (*.password, *.pass, .password.*)
- Add private key file patterns (*_private_key.txt, *.private, private_key.*)
- Add guardian contract database patterns (*.guardian.db, guardian_contracts/)
- Add multi-chain wallet data patterns (.
2026-03-18 20:52:52 +01:00

37 lines
1.0 KiB
Plaintext

# AITBC Deployment Configuration Template
# Copy this file to .env.deploy and fill in your actual values
# NEVER commit the actual .env.deploy file with real credentials
# === REQUIRED DEPLOYMENT SETTINGS ===
CONTAINER_NAME="aitbc"
CONTAINER_IP="YOUR_CONTAINER_IP"
PROJECT_DIR="/path/to/your/aitbc"
SSH_ALIAS="your-ssh-alias"
SSH_KEY_PATH="/path/to/your/private/key"
# === OPTIONAL SECURITY SETTINGS ===
# SSH connection timeout (seconds)
SSH_TIMEOUT=30
# Backup settings
CREATE_BACKUP=true
BACKUP_RETENTION_DAYS=7
# Service restart settings
RESTART_SERVICES=true
SERVICE_STARTUP_TIMEOUT=60
# === EXAMPLE VALUES ===
# CONTAINER_NAME="aitbc"
# CONTAINER_IP="192.168.1.100"
# PROJECT_DIR="/home/user/aitbc"
# SSH_ALIAS="user@container-ip"
# SSH_KEY_PATH="/home/user/.ssh/id_rsa"
# === SECURITY NOTES ===
# 1. Never commit this file with real credentials
# 2. Use SSH keys instead of passwords
# 3. Restrict file permissions: chmod 600 .env.deploy
# 4. Use SSH config file for complex connection settings
# 5. Consider using a secrets management system for production