# PostgreSQL Configuration Template
#
# IMPORTANT: This file is for LOCAL DEVELOPMENT ONLY!
# For production deployments, use Jenkins credentials instead of .env files
#
# Local Development Setup:
# 1. Copy this file to .env: cp .env.example .env
# 2. Edit .env with your local development values
# 3. Run: docker-compose up -d
#
# For Jenkins/Production deployments:
# - Configure credentials in Jenkins UI
# - Do NOT create .env file
# - Pipeline uses Jenkins credentials store instead

# Database Configuration (for local development only)
POSTGRES_DB=postgres
POSTGRES_USER=postgres
POSTGRES_PASSWORD=dev_password_here

# Project Configuration (for local development only)
PROJECT_NAME="Local PostgreSQL"
PROJECT_SCHEMA=none  # Set to schema file name (e.g., datashield-schema.sql) or leave as 'none'

# Backup Configuration (for local development only)
BACKUP_SCHEDULE=0 2 * * *
BACKUP_RETENTION=7

# Jenkins Production Credentials Setup:
# ---------------------------------------
# 1. Go to: Jenkins → Manage Jenkins → Manage Credentials → (global) → Add Credentials
# 2. Create these credentials:
#    - postgres-password (Secret Text): Your production PostgreSQL password
#    - postgres-db (String, optional): Database name (default: postgres)
#    - postgres-user (String, optional): Database user (default: postgres)
# 3. Jenkins pipeline will automatically use these credentials
# - For production, consider using Docker secrets or external secret management