Joakim
4f8da38ca6
## New Features - **Nextcloud Role**: Complete cloud storage deployment using Podman Quadlet - FPM variant with Caddy reverse proxy and FastCGI - PostgreSQL database via Unix socket - Valkey/Redis for app-level caching and file locking - Automatic HTTPS with Let's Encrypt via Caddy - Dual-root pattern: Caddy serves static assets, FPM handles PHP - **Split Caching Strategy**: Redis caching WITHOUT Redis sessions - Custom redis.config.php template for app-level caching only - File-based PHP sessions for stability (avoids session lock issues) - Prevents cascading failures from session lock contention - Documented in role README with detailed rationale ## Infrastructure Updates - **Socket Permissions**: Update PostgreSQL and Valkey to mode 777 - Required for containers that switch users (root → www-data) - Nextcloud container loses supplementary groups on user switch - Security maintained via password authentication (scram-sha-256, requirepass) - Documented socket permission architecture in docs/ - **PostgreSQL**: Export client group GID as fact for dependent roles - **Valkey**: Export client group GID as fact, update socket fix service ## Documentation - New: docs/socket-permissions-architecture.md - Explains 777 vs 770 socket permission trade-offs - Documents why group-based access doesn't work for user-switching containers - Provides TCP alternative for stricter security requirements - Updated: All role READMEs with socket permission notes - New: Nextcloud README with comprehensive deployment, troubleshooting, and Redis architecture documentation ## Configuration - host_vars: Add Nextcloud vault variables and configuration - site.yml: Include Nextcloud role in main playbook ## Technical Details **Why disable Redis sessions?** The official Nextcloud container enables Redis session handling via REDIS_HOST env var, which causes severe performance issues: 1. Session lock contention under high concurrency (browser parallel asset requests) 2. Infinite lock retries (default lock_retries=-1) blocking FPM workers 3. Timeout orphaning: reverse proxy kills connection, worker keeps lock 4. Worker pool exhaustion: all 5 default workers blocked on same session lock 5. Cascading failure: new requests queue, more timeouts, more orphaned locks Solution: Use file-based sessions (reliable, fast for single-server) while keeping Redis for distributed cache and transactional file locking via custom config file. This provides optimal performance without the complexity of Redis session debugging. Tested: Fresh deployment on arch-vps (69.62.119.31) Domain: https://cloud.jnss.me/
65 lines
2.2 KiB
YAML
65 lines
2.2 KiB
YAML
---
|
|
# =================================================================
|
|
# PostgreSQL Infrastructure Role - Simplified Configuration
|
|
# =================================================================
|
|
# Provides PostgreSQL database server as shared infrastructure
|
|
# Applications manage their own databases/users
|
|
|
|
# =================================================================
|
|
# Essential Configuration
|
|
# =================================================================
|
|
|
|
# Service Management
|
|
postgresql_service_enabled: true
|
|
postgresql_service_state: "started"
|
|
|
|
# Network Security
|
|
postgresql_listen_addresses: "localhost"
|
|
postgresql_port: 5432
|
|
|
|
# Unix Socket Configuration
|
|
postgresql_unix_socket_enabled: true
|
|
postgresql_unix_socket_directories: "/var/run/postgresql"
|
|
# Note: 0777 allows containers running as any UID to access the socket
|
|
# This is needed for containers that start as root and switch to unprivileged users (e.g., Nextcloud)
|
|
# Security is maintained via password authentication (scram-sha-256)
|
|
# Alternative: Use TCP on 127.0.0.1:5432 (see documentation)
|
|
postgresql_unix_socket_permissions: "0777"
|
|
|
|
# Group-Based Access Control
|
|
postgresql_client_group: "postgres-clients"
|
|
postgresql_client_group_create: true
|
|
|
|
# Authentication
|
|
postgresql_auth_method: "scram-sha-256"
|
|
|
|
# Database Cluster Setup
|
|
postgresql_encoding: "UTF8"
|
|
postgresql_locale: "C.UTF-8"
|
|
postgresql_data_checksums: true
|
|
|
|
# Security
|
|
postgresql_systemd_security: true
|
|
|
|
# =================================================================
|
|
# Optional Performance (Conservative Defaults)
|
|
# =================================================================
|
|
|
|
# Basic performance settings - PostgreSQL defaults are excellent
|
|
postgresql_max_connections: 100
|
|
postgresql_shared_buffers: "128MB"
|
|
|
|
# =================================================================
|
|
# Infrastructure Notes
|
|
# =================================================================
|
|
# This role provides minimal PostgreSQL infrastructure
|
|
# Applications should create their own databases/users:
|
|
#
|
|
# - postgresql_user:
|
|
# name: myapp
|
|
# password: "{{ vault_myapp_password }}"
|
|
# - postgresql_db:
|
|
# name: myapp
|
|
# owner: myapp
|
|
#
|
|
# PostgreSQL's built-in defaults are used for everything else |