COMPREHENSIVE CHANGES: INFRASTRUCTURE MIGRATION: - Migrated services to Docker Swarm on OMV800 (192.168.50.229) - Deployed PostgreSQL database for Vaultwarden migration - Updated all stack configurations for Docker Swarm compatibility - Added comprehensive monitoring stack (Prometheus, Grafana, Blackbox) - Implemented proper secret management for all services VAULTWARDEN POSTGRESQL MIGRATION: - Attempted migration from SQLite to PostgreSQL for NFS compatibility - Created PostgreSQL stack with proper user/password configuration - Built custom Vaultwarden image with PostgreSQL support - Troubleshot persistent SQLite fallback issue despite PostgreSQL config - Identified known issue where Vaultwarden silently falls back to SQLite - Added ENABLE_DB_WAL=false to prevent filesystem compatibility issues - Current status: Old Vaultwarden on lenovo410 still working, new one has config issues PAPERLESS SERVICES: - Successfully deployed Paperless-NGX and Paperless-AI on OMV800 - Both services running on ports 8000 and 3000 respectively - Caddy configuration updated for external access - Services accessible via paperless.pressmess.duckdns.org and paperless-ai.pressmess.duckdns.org CADDY CONFIGURATION: - Updated Caddyfile on Surface (192.168.50.254) for new service locations - Fixed Vaultwarden reverse proxy to point to new Docker Swarm service - Removed old notification hub reference that was causing conflicts - All services properly configured for external access via DuckDNS BACKUP AND DISCOVERY: - Created comprehensive backup system for all hosts - Generated detailed discovery reports for infrastructure analysis - Implemented automated backup validation scripts - Created migration progress tracking and verification reports MONITORING STACK: - Deployed Prometheus, Grafana, and Blackbox monitoring - Created infrastructure and system overview dashboards - Added proper service discovery and alerting configuration - Implemented performance monitoring for all critical services DOCUMENTATION: - Reorganized documentation into logical structure - Created comprehensive migration playbook and troubleshooting guides - Added hardware specifications and optimization recommendations - Documented all configuration changes and service dependencies CURRENT STATUS: - Paperless services: ✅ Working and accessible externally - Vaultwarden: ❌ PostgreSQL configuration issues, old instance still working - Monitoring: ✅ Deployed and operational - Caddy: ✅ Updated and working for external access - PostgreSQL: ✅ Database running, connection issues with Vaultwarden NEXT STEPS: - Continue troubleshooting Vaultwarden PostgreSQL configuration - Consider alternative approaches for Vaultwarden migration - Validate all external service access - Complete final migration validation TECHNICAL NOTES: - Used Docker Swarm for orchestration on OMV800 - Implemented proper secret management for sensitive data - Added comprehensive logging and monitoring - Created automated backup and validation scripts
45 lines
1.0 KiB
YAML
45 lines
1.0 KiB
YAML
# Docker Secrets Mapping
|
|
# Maps environment variables to Docker secrets
|
|
|
|
secrets_mapping:
|
|
postgresql:
|
|
POSTGRES_PASSWORD: pg_root_password
|
|
POSTGRES_DB_PASSWORD: pg_root_password
|
|
|
|
mariadb:
|
|
MYSQL_ROOT_PASSWORD: mariadb_root_password
|
|
MARIADB_ROOT_PASSWORD: mariadb_root_password
|
|
|
|
redis:
|
|
REDIS_PASSWORD: redis_password
|
|
|
|
nextcloud:
|
|
MYSQL_PASSWORD: nextcloud_db_password
|
|
NEXTCLOUD_ADMIN_PASSWORD: nextcloud_admin_password
|
|
|
|
immich:
|
|
DB_PASSWORD: immich_db_password
|
|
|
|
paperless:
|
|
PAPERLESS_SECRET_KEY: paperless_secret_key
|
|
|
|
vaultwarden:
|
|
ADMIN_TOKEN: vaultwarden_admin_token
|
|
|
|
homeassistant:
|
|
SUPERVISOR_TOKEN: ha_api_token
|
|
|
|
grafana:
|
|
GF_SECURITY_ADMIN_PASSWORD: grafana_admin_password
|
|
|
|
jellyfin:
|
|
JELLYFIN_API_KEY: jellyfin_api_key
|
|
|
|
gitea:
|
|
GITEA__security__SECRET_KEY: gitea_secret_key
|
|
|
|
# File secrets (certificates, keys)
|
|
file_secrets:
|
|
tls_certificate: /run/secrets/tls_certificate
|
|
tls_private_key: /run/secrets/tls_private_key
|