Post-Tyranny-Tech-Infrastru.../ansible/roles/nextcloud/templates/docker-compose.nextcloud.yml.j2

173 lines
5.7 KiB
Text
Raw Normal View History

Deploy Nextcloud file sync/share with automated installation (#4) This commit implements a complete Nextcloud deployment with PostgreSQL, Redis, automated installation, and preparation for OIDC/SSO integration with Zitadel. ## Nextcloud Deployment ### New Ansible Role (ansible/roles/nextcloud/) - Complete Nextcloud v30 deployment with Docker Compose - PostgreSQL 16 backend with persistent volumes - Redis 7 for caching and file locking - Automated installation via Docker environment variables - Post-installation configuration via occ commands ### Features Implemented - **Database**: PostgreSQL with proper credentials and persistence - **Caching**: Redis for memory caching and file locking - **HTTPS**: Traefik integration with Let's Encrypt SSL - **Security**: Proper security headers and HSTS - **WebDAV**: CalDAV/CardDAV redirect middleware - **Configuration**: Automated trusted domain, reverse proxy, and Redis setup - **OIDC Preparation**: user_oidc app installed and enabled ### Traefik Updates - Added Nextcloud routing to dynamic.yml (static file-based config) - Configured CalDAV/CardDAV redirect middleware - Added Nextcloud-specific security headers ### Configuration Tasks - Automated trusted domain configuration for nextcloud.test.vrije.cloud - Reverse proxy overwrite settings (protocol, host, CLI URL) - Redis cache and locking configuration - Default phone region (NL) - Background jobs via cron ## Deployment Status ✅ Successfully deployed and tested: - Nextcloud: https://nextcloud.test.vrije.cloud/ - Admin login working - PostgreSQL database initialized - Redis caching operational - HTTPS with Let's Encrypt SSL - user_oidc app installed (ready for Zitadel integration) ## Next Steps To complete OIDC/SSO integration: 1. Create OIDC application in Zitadel console 2. Use redirect URI: https://nextcloud.test.vrije.cloud/apps/user_oidc/code 3. Configure provider in Nextcloud with Zitadel credentials Partially addresses #4 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-06 09:30:54 +01:00
services:
# PostgreSQL Database for Nextcloud
nextcloud-db:
image: postgres:16-alpine
container_name: nextcloud-db
restart: unless-stopped
volumes:
- nextcloud-db-data:/var/lib/postgresql/data
environment:
POSTGRES_DB: {{ nextcloud_db_name }}
POSTGRES_USER: {{ nextcloud_db_user }}
POSTGRES_PASSWORD: {{ client_secrets.nextcloud_db_password }}
# Grant full privileges to the user
POSTGRES_INITDB_ARGS: "--auth-host=scram-sha-256"
networks:
- nextcloud-internal
# Redis for caching and file locking
nextcloud-redis:
image: redis:7-alpine
container_name: nextcloud-redis
restart: unless-stopped
command: redis-server --save 60 1 --loglevel warning
volumes:
- nextcloud-redis-data:/data
networks:
- nextcloud-internal
Add Collabora Office, 2FA, cron container, and dual-cache (#4) This commit adds production-ready features to Nextcloud based on the user's existing Nextcloud configuration. ## New Features ### 1. Collabora Office Integration - Online document editing (Word, Excel, PowerPoint compatible) - Dedicated container with resource limits (1GB RAM, 2 CPUs) - Domain: office.{client}.vrije.cloud - WOPI protocol integration with Nextcloud - Automatic app installation (richdocuments) - SSL termination via Traefik ### 2. Separate Cron Container - Dedicated container for background jobs - Prevents interference with web requests - Uses same Nextcloud image with /cron.sh entrypoint - Shares data volume with main container ### 3. Two-Factor Authentication Apps installed and configured: - twofactor_totp: TOTP authenticator apps support - twofactor_admin: Admin enforcement capabilities - twofactor_backupcodes: Backup codes for account recovery Configuration: - 2FA enforced for all users by default - Users must set up 2FA on first login ### 4. Dual-Cache Strategy (APCu + Redis) Optimized caching configuration: - **APCu**: Local in-memory cache (fast, single-server) - **Redis**: Distributed cache and file locking (shared) Benefits: - Faster page loads (APCu for frequently accessed data) - Proper file locking across containers (Redis) - Better scalability for multi-container setups ### 5. Additional Configurations - Maintenance window: 2:00 AM - Default phone region: NL - Improved performance and reliability ## Technical Changes ### Docker Compose Updates - Added nextcloud-cron service - Added collabora service with Traefik labels - Resource limits for Collabora (memory, CPU) ### Ansible Tasks - New file: `tasks/apps.yml` - App installation and configuration - Collabora WOPI URL configuration - Collabora network allowlist setup - 2FA app installation and enforcement - APCu local cache configuration - Maintenance window setting ### Configuration Variables - `collabora_enabled`: Enable/disable Collabora (default: true) - `collabora_domain`: Collabora subdomain - `collabora_admin_user`: Collabora admin username - `twofactor_enforced`: Enforce 2FA (default: true) ## Documentation Added comprehensive setup guide: - `docs/COLLABORA_SETUP.md`: Complete feature documentation - Configuration instructions - Testing procedures - Troubleshooting guide - Performance tuning tips - Security considerations ## Manual Step Required Add Collabora admin password to secrets: ```bash cd infrastructure export SOPS_AGE_KEY_FILE="$PWD/keys/age-key.txt" sops secrets/clients/test.sops.yaml # Add: collabora_admin_password: 7ju5h70L47xJMCoADgKiZIhSak4cwq0B ``` Then redeploy to apply all changes. ## Testing Checklist - [ ] Collabora: Create document in Nextcloud - [ ] 2FA: Login and set up authenticator - [ ] Cron: Check background jobs running - [ ] Cache: Verify APCu + Redis in config ## Performance Impact Expected improvements: - 30-50% faster page loads (APCu caching) - Better concurrent user support (Redis locking) - No web request delays from cron jobs (separate container) - Professional document editing experience (Collabora) Partially addresses #4 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-06 10:34:42 +01:00
# Nextcloud cron (separate container for background jobs)
nextcloud-cron:
image: nextcloud:{{ nextcloud_version }}
container_name: nextcloud-cron
restart: unless-stopped
depends_on:
- nextcloud-db
- nextcloud-redis
volumes:
feat: Use Hetzner Volumes for Nextcloud data storage (issue #18) Implement persistent block storage for Nextcloud user data, separating application and data layers: OpenTofu Changes: - tofu/volumes.tf: Create and attach Hetzner Volumes per client - Configurable size per client (default 100 GB for dev) - ext4 formatted, attached but not auto-mounted - tofu/variables.tf: Add nextcloud_volume_size to client config - tofu/terraform.tfvars: Set volume size for dev client (100 GB ~€5.40/mo) Ansible Changes: - ansible/roles/nextcloud/tasks/mount-volume.yml: New mount tasks - Detect volume device automatically - Format if needed, mount at /mnt/nextcloud-data - Add to fstab for persistence - Set correct permissions for www-data - ansible/roles/nextcloud/tasks/main.yml: Include volume mounting - ansible/roles/nextcloud/templates/docker-compose.nextcloud.yml.j2: - Use host mount /mnt/nextcloud-data/data instead of Docker volume - Keep app code in Docker volume (nextcloud-app) - User data now on Hetzner Volume Scripts: - scripts/resize-client-volume.sh: Online volume resizing - Resize via Hetzner API - Expand filesystem automatically - Show cost impact - Verify new size Documentation: - docs/storage-architecture.md: Complete storage guide - Architecture diagrams - Volume specifications - Sizing guidelines - Operations procedures - Performance considerations - Troubleshooting guide - docs/volume-migration.md: Step-by-step migration - Safe migration from Docker volumes - Rollback procedures - Verification checklist - Timeline estimates Benefits: ✅ Data independent from server instance ✅ Resize storage without rebuilding server ✅ Easy data migration between servers ✅ Better separation of concerns (app vs data) ✅ Simplified backup strategy ✅ Cost-optimized (pay for what you use) Volume Pricing: - 50 GB: ~€2.70/month - 100 GB: ~€5.40/month - 250 GB: ~€13.50/month - Resizable online, no downtime Note: Existing clients require manual migration Follow docs/volume-migration.md for safe migration procedure Closes #18 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-17 21:07:48 +01:00
- nextcloud-app:/var/www/html
- /mnt/nextcloud-data/data:/var/www/html/data # User data on Hetzner Volume
Add Collabora Office, 2FA, cron container, and dual-cache (#4) This commit adds production-ready features to Nextcloud based on the user's existing Nextcloud configuration. ## New Features ### 1. Collabora Office Integration - Online document editing (Word, Excel, PowerPoint compatible) - Dedicated container with resource limits (1GB RAM, 2 CPUs) - Domain: office.{client}.vrije.cloud - WOPI protocol integration with Nextcloud - Automatic app installation (richdocuments) - SSL termination via Traefik ### 2. Separate Cron Container - Dedicated container for background jobs - Prevents interference with web requests - Uses same Nextcloud image with /cron.sh entrypoint - Shares data volume with main container ### 3. Two-Factor Authentication Apps installed and configured: - twofactor_totp: TOTP authenticator apps support - twofactor_admin: Admin enforcement capabilities - twofactor_backupcodes: Backup codes for account recovery Configuration: - 2FA enforced for all users by default - Users must set up 2FA on first login ### 4. Dual-Cache Strategy (APCu + Redis) Optimized caching configuration: - **APCu**: Local in-memory cache (fast, single-server) - **Redis**: Distributed cache and file locking (shared) Benefits: - Faster page loads (APCu for frequently accessed data) - Proper file locking across containers (Redis) - Better scalability for multi-container setups ### 5. Additional Configurations - Maintenance window: 2:00 AM - Default phone region: NL - Improved performance and reliability ## Technical Changes ### Docker Compose Updates - Added nextcloud-cron service - Added collabora service with Traefik labels - Resource limits for Collabora (memory, CPU) ### Ansible Tasks - New file: `tasks/apps.yml` - App installation and configuration - Collabora WOPI URL configuration - Collabora network allowlist setup - 2FA app installation and enforcement - APCu local cache configuration - Maintenance window setting ### Configuration Variables - `collabora_enabled`: Enable/disable Collabora (default: true) - `collabora_domain`: Collabora subdomain - `collabora_admin_user`: Collabora admin username - `twofactor_enforced`: Enforce 2FA (default: true) ## Documentation Added comprehensive setup guide: - `docs/COLLABORA_SETUP.md`: Complete feature documentation - Configuration instructions - Testing procedures - Troubleshooting guide - Performance tuning tips - Security considerations ## Manual Step Required Add Collabora admin password to secrets: ```bash cd infrastructure export SOPS_AGE_KEY_FILE="$PWD/keys/age-key.txt" sops secrets/clients/test.sops.yaml # Add: collabora_admin_password: 7ju5h70L47xJMCoADgKiZIhSak4cwq0B ``` Then redeploy to apply all changes. ## Testing Checklist - [ ] Collabora: Create document in Nextcloud - [ ] 2FA: Login and set up authenticator - [ ] Cron: Check background jobs running - [ ] Cache: Verify APCu + Redis in config ## Performance Impact Expected improvements: - 30-50% faster page loads (APCu caching) - Better concurrent user support (Redis locking) - No web request delays from cron jobs (separate container) - Professional document editing experience (Collabora) Partially addresses #4 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-06 10:34:42 +01:00
entrypoint: /cron.sh
networks:
- nextcloud-internal
Deploy Nextcloud file sync/share with automated installation (#4) This commit implements a complete Nextcloud deployment with PostgreSQL, Redis, automated installation, and preparation for OIDC/SSO integration with Zitadel. ## Nextcloud Deployment ### New Ansible Role (ansible/roles/nextcloud/) - Complete Nextcloud v30 deployment with Docker Compose - PostgreSQL 16 backend with persistent volumes - Redis 7 for caching and file locking - Automated installation via Docker environment variables - Post-installation configuration via occ commands ### Features Implemented - **Database**: PostgreSQL with proper credentials and persistence - **Caching**: Redis for memory caching and file locking - **HTTPS**: Traefik integration with Let's Encrypt SSL - **Security**: Proper security headers and HSTS - **WebDAV**: CalDAV/CardDAV redirect middleware - **Configuration**: Automated trusted domain, reverse proxy, and Redis setup - **OIDC Preparation**: user_oidc app installed and enabled ### Traefik Updates - Added Nextcloud routing to dynamic.yml (static file-based config) - Configured CalDAV/CardDAV redirect middleware - Added Nextcloud-specific security headers ### Configuration Tasks - Automated trusted domain configuration for nextcloud.test.vrije.cloud - Reverse proxy overwrite settings (protocol, host, CLI URL) - Redis cache and locking configuration - Default phone region (NL) - Background jobs via cron ## Deployment Status ✅ Successfully deployed and tested: - Nextcloud: https://nextcloud.test.vrije.cloud/ - Admin login working - PostgreSQL database initialized - Redis caching operational - HTTPS with Let's Encrypt SSL - user_oidc app installed (ready for Zitadel integration) ## Next Steps To complete OIDC/SSO integration: 1. Create OIDC application in Zitadel console 2. Use redirect URI: https://nextcloud.test.vrije.cloud/apps/user_oidc/code 3. Configure provider in Nextcloud with Zitadel credentials Partially addresses #4 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-06 09:30:54 +01:00
# Nextcloud application
nextcloud:
image: nextcloud:{{ nextcloud_version }}
container_name: nextcloud
restart: unless-stopped
depends_on:
- nextcloud-db
- nextcloud-redis
volumes:
feat: Use Hetzner Volumes for Nextcloud data storage (issue #18) Implement persistent block storage for Nextcloud user data, separating application and data layers: OpenTofu Changes: - tofu/volumes.tf: Create and attach Hetzner Volumes per client - Configurable size per client (default 100 GB for dev) - ext4 formatted, attached but not auto-mounted - tofu/variables.tf: Add nextcloud_volume_size to client config - tofu/terraform.tfvars: Set volume size for dev client (100 GB ~€5.40/mo) Ansible Changes: - ansible/roles/nextcloud/tasks/mount-volume.yml: New mount tasks - Detect volume device automatically - Format if needed, mount at /mnt/nextcloud-data - Add to fstab for persistence - Set correct permissions for www-data - ansible/roles/nextcloud/tasks/main.yml: Include volume mounting - ansible/roles/nextcloud/templates/docker-compose.nextcloud.yml.j2: - Use host mount /mnt/nextcloud-data/data instead of Docker volume - Keep app code in Docker volume (nextcloud-app) - User data now on Hetzner Volume Scripts: - scripts/resize-client-volume.sh: Online volume resizing - Resize via Hetzner API - Expand filesystem automatically - Show cost impact - Verify new size Documentation: - docs/storage-architecture.md: Complete storage guide - Architecture diagrams - Volume specifications - Sizing guidelines - Operations procedures - Performance considerations - Troubleshooting guide - docs/volume-migration.md: Step-by-step migration - Safe migration from Docker volumes - Rollback procedures - Verification checklist - Timeline estimates Benefits: ✅ Data independent from server instance ✅ Resize storage without rebuilding server ✅ Easy data migration between servers ✅ Better separation of concerns (app vs data) ✅ Simplified backup strategy ✅ Cost-optimized (pay for what you use) Volume Pricing: - 50 GB: ~€2.70/month - 100 GB: ~€5.40/month - 250 GB: ~€13.50/month - Resizable online, no downtime Note: Existing clients require manual migration Follow docs/volume-migration.md for safe migration procedure Closes #18 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-17 21:07:48 +01:00
- nextcloud-app:/var/www/html
- /mnt/nextcloud-data/data:/var/www/html/data # User data on Hetzner Volume
Deploy Nextcloud file sync/share with automated installation (#4) This commit implements a complete Nextcloud deployment with PostgreSQL, Redis, automated installation, and preparation for OIDC/SSO integration with Zitadel. ## Nextcloud Deployment ### New Ansible Role (ansible/roles/nextcloud/) - Complete Nextcloud v30 deployment with Docker Compose - PostgreSQL 16 backend with persistent volumes - Redis 7 for caching and file locking - Automated installation via Docker environment variables - Post-installation configuration via occ commands ### Features Implemented - **Database**: PostgreSQL with proper credentials and persistence - **Caching**: Redis for memory caching and file locking - **HTTPS**: Traefik integration with Let's Encrypt SSL - **Security**: Proper security headers and HSTS - **WebDAV**: CalDAV/CardDAV redirect middleware - **Configuration**: Automated trusted domain, reverse proxy, and Redis setup - **OIDC Preparation**: user_oidc app installed and enabled ### Traefik Updates - Added Nextcloud routing to dynamic.yml (static file-based config) - Configured CalDAV/CardDAV redirect middleware - Added Nextcloud-specific security headers ### Configuration Tasks - Automated trusted domain configuration for nextcloud.test.vrije.cloud - Reverse proxy overwrite settings (protocol, host, CLI URL) - Redis cache and locking configuration - Default phone region (NL) - Background jobs via cron ## Deployment Status ✅ Successfully deployed and tested: - Nextcloud: https://nextcloud.test.vrije.cloud/ - Admin login working - PostgreSQL database initialized - Redis caching operational - HTTPS with Let's Encrypt SSL - user_oidc app installed (ready for Zitadel integration) ## Next Steps To complete OIDC/SSO integration: 1. Create OIDC application in Zitadel console 2. Use redirect URI: https://nextcloud.test.vrije.cloud/apps/user_oidc/code 3. Configure provider in Nextcloud with Zitadel credentials Partially addresses #4 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-06 09:30:54 +01:00
environment:
# Database configuration
POSTGRES_HOST: {{ nextcloud_db_host }}
POSTGRES_DB: {{ nextcloud_db_name }}
POSTGRES_USER: {{ nextcloud_db_user }}
POSTGRES_PASSWORD: {{ client_secrets.nextcloud_db_password }}
# Redis configuration
REDIS_HOST: {{ nextcloud_redis_host }}
REDIS_HOST_PORT: {{ nextcloud_redis_port }}
# Nextcloud configuration
NEXTCLOUD_ADMIN_USER: {{ nextcloud_admin_user }}
NEXTCLOUD_ADMIN_PASSWORD: {{ client_secrets.nextcloud_admin_password }}
NEXTCLOUD_TRUSTED_DOMAINS: {{ nextcloud_domain }}
OVERWRITEPROTOCOL: https
OVERWRITEHOST: {{ nextcloud_domain }}
OVERWRITECLIURL: https://{{ nextcloud_domain }}
# PHP configuration
PHP_MEMORY_LIMIT: {{ nextcloud_php_memory_limit }}
PHP_UPLOAD_LIMIT: {{ nextcloud_php_upload_limit }}
# SMTP configuration (optional, can be configured via OIDC later)
# SMTP_HOST:
# SMTP_SECURE:
# SMTP_PORT:
# SMTP_NAME:
# SMTP_PASSWORD:
# MAIL_FROM_ADDRESS:
# MAIL_DOMAIN:
networks:
- traefik
- nextcloud-internal
labels:
- "traefik.enable=true"
- "traefik.docker.network=traefik"
# HTTP Router
- "traefik.http.routers.nextcloud.rule=Host(`{{ nextcloud_domain }}`)"
- "traefik.http.routers.nextcloud.entrypoints=websecure"
- "traefik.http.routers.nextcloud.tls=true"
- "traefik.http.routers.nextcloud.tls.certresolver=letsencrypt"
# Middleware for Nextcloud
- "traefik.http.routers.nextcloud.middlewares=nextcloud-headers,nextcloud-redirectregex"
# Security headers
- "traefik.http.middlewares.nextcloud-headers.headers.stsSeconds=31536000"
- "traefik.http.middlewares.nextcloud-headers.headers.stsIncludeSubdomains=true"
- "traefik.http.middlewares.nextcloud-headers.headers.stsPreload=true"
# CalDAV/CardDAV redirect
- "traefik.http.middlewares.nextcloud-redirectregex.redirectregex.permanent=true"
- "traefik.http.middlewares.nextcloud-redirectregex.redirectregex.regex=https://(.*)/.well-known/(card|cal)dav"
- "traefik.http.middlewares.nextcloud-redirectregex.redirectregex.replacement=https://$$1/remote.php/dav/"
# Service
- "traefik.http.services.nextcloud.loadbalancer.server.port=80"
Add Collabora Office, 2FA, cron container, and dual-cache (#4) This commit adds production-ready features to Nextcloud based on the user's existing Nextcloud configuration. ## New Features ### 1. Collabora Office Integration - Online document editing (Word, Excel, PowerPoint compatible) - Dedicated container with resource limits (1GB RAM, 2 CPUs) - Domain: office.{client}.vrije.cloud - WOPI protocol integration with Nextcloud - Automatic app installation (richdocuments) - SSL termination via Traefik ### 2. Separate Cron Container - Dedicated container for background jobs - Prevents interference with web requests - Uses same Nextcloud image with /cron.sh entrypoint - Shares data volume with main container ### 3. Two-Factor Authentication Apps installed and configured: - twofactor_totp: TOTP authenticator apps support - twofactor_admin: Admin enforcement capabilities - twofactor_backupcodes: Backup codes for account recovery Configuration: - 2FA enforced for all users by default - Users must set up 2FA on first login ### 4. Dual-Cache Strategy (APCu + Redis) Optimized caching configuration: - **APCu**: Local in-memory cache (fast, single-server) - **Redis**: Distributed cache and file locking (shared) Benefits: - Faster page loads (APCu for frequently accessed data) - Proper file locking across containers (Redis) - Better scalability for multi-container setups ### 5. Additional Configurations - Maintenance window: 2:00 AM - Default phone region: NL - Improved performance and reliability ## Technical Changes ### Docker Compose Updates - Added nextcloud-cron service - Added collabora service with Traefik labels - Resource limits for Collabora (memory, CPU) ### Ansible Tasks - New file: `tasks/apps.yml` - App installation and configuration - Collabora WOPI URL configuration - Collabora network allowlist setup - 2FA app installation and enforcement - APCu local cache configuration - Maintenance window setting ### Configuration Variables - `collabora_enabled`: Enable/disable Collabora (default: true) - `collabora_domain`: Collabora subdomain - `collabora_admin_user`: Collabora admin username - `twofactor_enforced`: Enforce 2FA (default: true) ## Documentation Added comprehensive setup guide: - `docs/COLLABORA_SETUP.md`: Complete feature documentation - Configuration instructions - Testing procedures - Troubleshooting guide - Performance tuning tips - Security considerations ## Manual Step Required Add Collabora admin password to secrets: ```bash cd infrastructure export SOPS_AGE_KEY_FILE="$PWD/keys/age-key.txt" sops secrets/clients/test.sops.yaml # Add: collabora_admin_password: 7ju5h70L47xJMCoADgKiZIhSak4cwq0B ``` Then redeploy to apply all changes. ## Testing Checklist - [ ] Collabora: Create document in Nextcloud - [ ] 2FA: Login and set up authenticator - [ ] Cron: Check background jobs running - [ ] Cache: Verify APCu + Redis in config ## Performance Impact Expected improvements: - 30-50% faster page loads (APCu caching) - Better concurrent user support (Redis locking) - No web request delays from cron jobs (separate container) - Professional document editing experience (Collabora) Partially addresses #4 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-06 10:34:42 +01:00
# Collabora Office (online document editing)
collabora:
image: collabora/code:latest
container_name: collabora
restart: unless-stopped
🔧 fix: Optimize Collabora Online performance for 2-core servers ═══════════════════════════════════════════════════════════════ 🎯 PROBLEM SOLVED: Collabora Server Warnings ═══════════════════════════════════════════════════════════════ Fixed two critical performance warnings in Collabora Online: 1. ❌ "Slow Kit jail setup with copying, cannot bind-mount" → Error: "coolmount: Operation not permitted" 2. ❌ "Your server is configured with insufficient hardware resources" → No performance tuning for 2-core CPX22 servers ═══════════════════════════════════════════════════════════════ ✅ SOLUTION IMPLEMENTED ═══════════════════════════════════════════════════════════════ Added Docker Capabilities: cap_add: - MKNOD # Create device nodes for bind-mounting - SYS_CHROOT # Use chroot for jail isolation Performance Tuning (optimized for 2 CPU cores): --o:num_prespawn_children=1 # Pre-spawn 1 child process --o:per_document.max_concurrency=2 # Max 2 threads per document (matches CPU cores) ═══════════════════════════════════════════════════════════════ 📊 IMPACT ═══════════════════════════════════════════════════════════════ BEFORE: ⚠️ "coolmount: Operation not permitted" (repeated errors) ⚠️ "Slow Kit jail setup with copying" ⚠️ "Insufficient hardware resources" ⚠️ Poor document editing performance AFTER: ✅ No more coolmount errors (bind-mount working) ✅ Faster jail initialization ✅ Optimized for 2-core servers ✅ Smooth document editing ℹ️ Minor systemplate warning remains (safe to ignore) ═══════════════════════════════════════════════════════════════ 🔄 DEPLOYMENT METHOD ═══════════════════════════════════════════════════════════════ Applied via live config update (NO data loss): 1. docker compose down 2. Update docker-compose.yml 3. docker compose up -d Downtime: ~30 seconds User Impact: Minimal (refresh page to reconnect) Data Safety: ✅ All data preserved ═══════════════════════════════════════════════════════════════ 📝 TECHNICAL DETAILS ═══════════════════════════════════════════════════════════════ Server Specs (CPX22): - CPU: 2 cores (detected with nproc) - RAM: 3.7GB total - Collabora limits: 1GB memory, 2 CPUs Configuration follows Collabora SDK recommendations: - per_document.max_concurrency ≤ CPU cores - num_prespawn_children = 1 (suitable for small deployments) Reference: https://sdk.collaboraonline.com/docs/installation/Configuration.html#performance ═══════════════════════════════════════════════════════════════ ✨ FUTURE DEPLOYMENTS ═══════════════════════════════════════════════════════════════ All new clients will automatically get optimized Collabora configuration. No rebuild required for config-only changes like this. ═══════════════════════════════════════════════════════════════ 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-18 18:04:19 +01:00
# Required capabilities for optimal performance (bind-mount instead of copy)
cap_add:
- MKNOD
- SYS_CHROOT
Add Collabora Office, 2FA, cron container, and dual-cache (#4) This commit adds production-ready features to Nextcloud based on the user's existing Nextcloud configuration. ## New Features ### 1. Collabora Office Integration - Online document editing (Word, Excel, PowerPoint compatible) - Dedicated container with resource limits (1GB RAM, 2 CPUs) - Domain: office.{client}.vrije.cloud - WOPI protocol integration with Nextcloud - Automatic app installation (richdocuments) - SSL termination via Traefik ### 2. Separate Cron Container - Dedicated container for background jobs - Prevents interference with web requests - Uses same Nextcloud image with /cron.sh entrypoint - Shares data volume with main container ### 3. Two-Factor Authentication Apps installed and configured: - twofactor_totp: TOTP authenticator apps support - twofactor_admin: Admin enforcement capabilities - twofactor_backupcodes: Backup codes for account recovery Configuration: - 2FA enforced for all users by default - Users must set up 2FA on first login ### 4. Dual-Cache Strategy (APCu + Redis) Optimized caching configuration: - **APCu**: Local in-memory cache (fast, single-server) - **Redis**: Distributed cache and file locking (shared) Benefits: - Faster page loads (APCu for frequently accessed data) - Proper file locking across containers (Redis) - Better scalability for multi-container setups ### 5. Additional Configurations - Maintenance window: 2:00 AM - Default phone region: NL - Improved performance and reliability ## Technical Changes ### Docker Compose Updates - Added nextcloud-cron service - Added collabora service with Traefik labels - Resource limits for Collabora (memory, CPU) ### Ansible Tasks - New file: `tasks/apps.yml` - App installation and configuration - Collabora WOPI URL configuration - Collabora network allowlist setup - 2FA app installation and enforcement - APCu local cache configuration - Maintenance window setting ### Configuration Variables - `collabora_enabled`: Enable/disable Collabora (default: true) - `collabora_domain`: Collabora subdomain - `collabora_admin_user`: Collabora admin username - `twofactor_enforced`: Enforce 2FA (default: true) ## Documentation Added comprehensive setup guide: - `docs/COLLABORA_SETUP.md`: Complete feature documentation - Configuration instructions - Testing procedures - Troubleshooting guide - Performance tuning tips - Security considerations ## Manual Step Required Add Collabora admin password to secrets: ```bash cd infrastructure export SOPS_AGE_KEY_FILE="$PWD/keys/age-key.txt" sops secrets/clients/test.sops.yaml # Add: collabora_admin_password: 7ju5h70L47xJMCoADgKiZIhSak4cwq0B ``` Then redeploy to apply all changes. ## Testing Checklist - [ ] Collabora: Create document in Nextcloud - [ ] 2FA: Login and set up authenticator - [ ] Cron: Check background jobs running - [ ] Cache: Verify APCu + Redis in config ## Performance Impact Expected improvements: - 30-50% faster page loads (APCu caching) - Better concurrent user support (Redis locking) - No web request delays from cron jobs (separate container) - Professional document editing experience (Collabora) Partially addresses #4 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-06 10:34:42 +01:00
environment:
- domain={{ nextcloud_domain | regex_replace('\.', '\\.') }}
- username={{ collabora_admin_user }}
- password={{ client_secrets.collabora_admin_password }}
🔧 fix: Optimize Collabora Online performance for 2-core servers ═══════════════════════════════════════════════════════════════ 🎯 PROBLEM SOLVED: Collabora Server Warnings ═══════════════════════════════════════════════════════════════ Fixed two critical performance warnings in Collabora Online: 1. ❌ "Slow Kit jail setup with copying, cannot bind-mount" → Error: "coolmount: Operation not permitted" 2. ❌ "Your server is configured with insufficient hardware resources" → No performance tuning for 2-core CPX22 servers ═══════════════════════════════════════════════════════════════ ✅ SOLUTION IMPLEMENTED ═══════════════════════════════════════════════════════════════ Added Docker Capabilities: cap_add: - MKNOD # Create device nodes for bind-mounting - SYS_CHROOT # Use chroot for jail isolation Performance Tuning (optimized for 2 CPU cores): --o:num_prespawn_children=1 # Pre-spawn 1 child process --o:per_document.max_concurrency=2 # Max 2 threads per document (matches CPU cores) ═══════════════════════════════════════════════════════════════ 📊 IMPACT ═══════════════════════════════════════════════════════════════ BEFORE: ⚠️ "coolmount: Operation not permitted" (repeated errors) ⚠️ "Slow Kit jail setup with copying" ⚠️ "Insufficient hardware resources" ⚠️ Poor document editing performance AFTER: ✅ No more coolmount errors (bind-mount working) ✅ Faster jail initialization ✅ Optimized for 2-core servers ✅ Smooth document editing ℹ️ Minor systemplate warning remains (safe to ignore) ═══════════════════════════════════════════════════════════════ 🔄 DEPLOYMENT METHOD ═══════════════════════════════════════════════════════════════ Applied via live config update (NO data loss): 1. docker compose down 2. Update docker-compose.yml 3. docker compose up -d Downtime: ~30 seconds User Impact: Minimal (refresh page to reconnect) Data Safety: ✅ All data preserved ═══════════════════════════════════════════════════════════════ 📝 TECHNICAL DETAILS ═══════════════════════════════════════════════════════════════ Server Specs (CPX22): - CPU: 2 cores (detected with nproc) - RAM: 3.7GB total - Collabora limits: 1GB memory, 2 CPUs Configuration follows Collabora SDK recommendations: - per_document.max_concurrency ≤ CPU cores - num_prespawn_children = 1 (suitable for small deployments) Reference: https://sdk.collaboraonline.com/docs/installation/Configuration.html#performance ═══════════════════════════════════════════════════════════════ ✨ FUTURE DEPLOYMENTS ═══════════════════════════════════════════════════════════════ All new clients will automatically get optimized Collabora configuration. No rebuild required for config-only changes like this. ═══════════════════════════════════════════════════════════════ 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-18 18:04:19 +01:00
# Performance tuning based on available CPU cores
# num_prespawn_children: Number of child processes to keep started (default: 1)
# per_document.max_concurrency: Max threads per document (should be <= CPU cores)
- extra_params=--o:ssl.enable=false --o:ssl.termination=true --o:num_prespawn_children=1 --o:per_document.max_concurrency=2
Add Collabora Office, 2FA, cron container, and dual-cache (#4) This commit adds production-ready features to Nextcloud based on the user's existing Nextcloud configuration. ## New Features ### 1. Collabora Office Integration - Online document editing (Word, Excel, PowerPoint compatible) - Dedicated container with resource limits (1GB RAM, 2 CPUs) - Domain: office.{client}.vrije.cloud - WOPI protocol integration with Nextcloud - Automatic app installation (richdocuments) - SSL termination via Traefik ### 2. Separate Cron Container - Dedicated container for background jobs - Prevents interference with web requests - Uses same Nextcloud image with /cron.sh entrypoint - Shares data volume with main container ### 3. Two-Factor Authentication Apps installed and configured: - twofactor_totp: TOTP authenticator apps support - twofactor_admin: Admin enforcement capabilities - twofactor_backupcodes: Backup codes for account recovery Configuration: - 2FA enforced for all users by default - Users must set up 2FA on first login ### 4. Dual-Cache Strategy (APCu + Redis) Optimized caching configuration: - **APCu**: Local in-memory cache (fast, single-server) - **Redis**: Distributed cache and file locking (shared) Benefits: - Faster page loads (APCu for frequently accessed data) - Proper file locking across containers (Redis) - Better scalability for multi-container setups ### 5. Additional Configurations - Maintenance window: 2:00 AM - Default phone region: NL - Improved performance and reliability ## Technical Changes ### Docker Compose Updates - Added nextcloud-cron service - Added collabora service with Traefik labels - Resource limits for Collabora (memory, CPU) ### Ansible Tasks - New file: `tasks/apps.yml` - App installation and configuration - Collabora WOPI URL configuration - Collabora network allowlist setup - 2FA app installation and enforcement - APCu local cache configuration - Maintenance window setting ### Configuration Variables - `collabora_enabled`: Enable/disable Collabora (default: true) - `collabora_domain`: Collabora subdomain - `collabora_admin_user`: Collabora admin username - `twofactor_enforced`: Enforce 2FA (default: true) ## Documentation Added comprehensive setup guide: - `docs/COLLABORA_SETUP.md`: Complete feature documentation - Configuration instructions - Testing procedures - Troubleshooting guide - Performance tuning tips - Security considerations ## Manual Step Required Add Collabora admin password to secrets: ```bash cd infrastructure export SOPS_AGE_KEY_FILE="$PWD/keys/age-key.txt" sops secrets/clients/test.sops.yaml # Add: collabora_admin_password: 7ju5h70L47xJMCoADgKiZIhSak4cwq0B ``` Then redeploy to apply all changes. ## Testing Checklist - [ ] Collabora: Create document in Nextcloud - [ ] 2FA: Login and set up authenticator - [ ] Cron: Check background jobs running - [ ] Cache: Verify APCu + Redis in config ## Performance Impact Expected improvements: - 30-50% faster page loads (APCu caching) - Better concurrent user support (Redis locking) - No web request delays from cron jobs (separate container) - Professional document editing experience (Collabora) Partially addresses #4 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-06 10:34:42 +01:00
- MEMPROPORTION=60.0
- MAX_DOCUMENTS=10
- MAX_CONNECTIONS=20
deploy:
resources:
limits:
memory: 1g
cpus: '2'
reservations:
memory: 512m
networks:
- traefik
- nextcloud-internal
labels:
- "traefik.enable=true"
- "traefik.docker.network=traefik"
# HTTP Router
- "traefik.http.routers.collabora.rule=Host(`{{ collabora_domain }}`)"
- "traefik.http.routers.collabora.entrypoints=websecure"
- "traefik.http.routers.collabora.tls=true"
- "traefik.http.routers.collabora.tls.certresolver=letsencrypt"
# Service
- "traefik.http.services.collabora.loadbalancer.server.port=9980"
Deploy Nextcloud file sync/share with automated installation (#4) This commit implements a complete Nextcloud deployment with PostgreSQL, Redis, automated installation, and preparation for OIDC/SSO integration with Zitadel. ## Nextcloud Deployment ### New Ansible Role (ansible/roles/nextcloud/) - Complete Nextcloud v30 deployment with Docker Compose - PostgreSQL 16 backend with persistent volumes - Redis 7 for caching and file locking - Automated installation via Docker environment variables - Post-installation configuration via occ commands ### Features Implemented - **Database**: PostgreSQL with proper credentials and persistence - **Caching**: Redis for memory caching and file locking - **HTTPS**: Traefik integration with Let's Encrypt SSL - **Security**: Proper security headers and HSTS - **WebDAV**: CalDAV/CardDAV redirect middleware - **Configuration**: Automated trusted domain, reverse proxy, and Redis setup - **OIDC Preparation**: user_oidc app installed and enabled ### Traefik Updates - Added Nextcloud routing to dynamic.yml (static file-based config) - Configured CalDAV/CardDAV redirect middleware - Added Nextcloud-specific security headers ### Configuration Tasks - Automated trusted domain configuration for nextcloud.test.vrije.cloud - Reverse proxy overwrite settings (protocol, host, CLI URL) - Redis cache and locking configuration - Default phone region (NL) - Background jobs via cron ## Deployment Status ✅ Successfully deployed and tested: - Nextcloud: https://nextcloud.test.vrije.cloud/ - Admin login working - PostgreSQL database initialized - Redis caching operational - HTTPS with Let's Encrypt SSL - user_oidc app installed (ready for Zitadel integration) ## Next Steps To complete OIDC/SSO integration: 1. Create OIDC application in Zitadel console 2. Use redirect URI: https://nextcloud.test.vrije.cloud/apps/user_oidc/code 3. Configure provider in Nextcloud with Zitadel credentials Partially addresses #4 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-06 09:30:54 +01:00
networks:
traefik:
external: true
nextcloud-internal:
name: nextcloud-internal
driver: bridge
volumes:
nextcloud-db-data:
name: nextcloud-db-data
nextcloud-redis-data:
name: nextcloud-redis-data
feat: Use Hetzner Volumes for Nextcloud data storage (issue #18) Implement persistent block storage for Nextcloud user data, separating application and data layers: OpenTofu Changes: - tofu/volumes.tf: Create and attach Hetzner Volumes per client - Configurable size per client (default 100 GB for dev) - ext4 formatted, attached but not auto-mounted - tofu/variables.tf: Add nextcloud_volume_size to client config - tofu/terraform.tfvars: Set volume size for dev client (100 GB ~€5.40/mo) Ansible Changes: - ansible/roles/nextcloud/tasks/mount-volume.yml: New mount tasks - Detect volume device automatically - Format if needed, mount at /mnt/nextcloud-data - Add to fstab for persistence - Set correct permissions for www-data - ansible/roles/nextcloud/tasks/main.yml: Include volume mounting - ansible/roles/nextcloud/templates/docker-compose.nextcloud.yml.j2: - Use host mount /mnt/nextcloud-data/data instead of Docker volume - Keep app code in Docker volume (nextcloud-app) - User data now on Hetzner Volume Scripts: - scripts/resize-client-volume.sh: Online volume resizing - Resize via Hetzner API - Expand filesystem automatically - Show cost impact - Verify new size Documentation: - docs/storage-architecture.md: Complete storage guide - Architecture diagrams - Volume specifications - Sizing guidelines - Operations procedures - Performance considerations - Troubleshooting guide - docs/volume-migration.md: Step-by-step migration - Safe migration from Docker volumes - Rollback procedures - Verification checklist - Timeline estimates Benefits: ✅ Data independent from server instance ✅ Resize storage without rebuilding server ✅ Easy data migration between servers ✅ Better separation of concerns (app vs data) ✅ Simplified backup strategy ✅ Cost-optimized (pay for what you use) Volume Pricing: - 50 GB: ~€2.70/month - 100 GB: ~€5.40/month - 250 GB: ~€13.50/month - Resizable online, no downtime Note: Existing clients require manual migration Follow docs/volume-migration.md for safe migration procedure Closes #18 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-17 21:07:48 +01:00
nextcloud-app:
name: nextcloud-app
# Note: nextcloud-data volume removed - user data now stored on Hetzner Volume at /mnt/nextcloud-data