No description
Find a file
Pieter 8a88096619 🔧 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
.claude/agents feat: Implement per-client SSH key isolation 2026-01-17 19:50:30 +01:00
ansible 🔧 fix: Optimize Collabora Online performance for 2-core servers 2026-01-18 18:04:19 +01:00
clients feat: Implement client registry system (issue #12) 2026-01-17 20:24:53 +01:00
docs feat: Use Hetzner Volumes for Nextcloud data storage (issue #18) 2026-01-17 21:07:48 +01:00
keys 🚀 GREEN CLIENT DEPLOYMENT + CRITICAL SECURITY FIXES 2026-01-18 17:06:04 +01:00
scripts 🚀 GREEN CLIENT DEPLOYMENT + CRITICAL SECURITY FIXES 2026-01-18 17:06:04 +01:00
secrets 🚀 GREEN CLIENT DEPLOYMENT + CRITICAL SECURITY FIXES 2026-01-18 17:06:04 +01:00
tofu feat: Use Hetzner Volumes for Nextcloud data storage (issue #18) 2026-01-17 21:07:48 +01:00
.gitignore 🚀 GREEN CLIENT DEPLOYMENT + CRITICAL SECURITY FIXES 2026-01-18 17:06:04 +01:00
.sops.yaml Complete SOPS secrets management setup (#5) 2025-12-27 14:23:36 +01:00
PROJECT_REFERENCE.md feat: Complete Authentik SSO integration with automated OIDC setup 2026-01-08 16:56:19 +01:00
README.md feat: Automate SSH key and secrets generation in deployment scripts 2026-01-17 20:04:29 +01:00
SECURITY-NOTE-tokens.md docs: Complete blue client deployment test and security review 2026-01-17 21:40:12 +01:00
TEST-REPORT-blue-client.md docs: Complete blue client deployment test and security review 2026-01-17 21:40:12 +01:00

Post-X Society Multi-Tenant Infrastructure

Infrastructure as Code for a scalable multi-tenant VPS platform running Nextcloud (file sync/share) on Hetzner Cloud.

🏗️ Architecture

  • Provisioning: OpenTofu (open source Terraform fork)
  • Configuration: Ansible with dynamic inventory
  • Secrets: SOPS + Age encryption
  • Hosting: Hetzner Cloud (EU-based, GDPR-compliant)
  • Identity: Authentik (OAuth2/OIDC SSO, MIT license)
  • Storage: Nextcloud (German company, AGPL 3.0)

📁 Repository Structure

infrastructure/
├── .claude/agents/          # AI agent definitions for specialized tasks
├── docs/                    # Architecture decisions and runbooks
├── tofu/                    # OpenTofu configurations for Hetzner
├── ansible/                 # Ansible playbooks and roles
├── secrets/                 # SOPS-encrypted secrets (git-safe)
├── docker/                  # Docker Compose configurations
└── scripts/                 # Deployment and management scripts

🚀 Quick Start

Prerequisites

The fastest way to deploy a client:

# 1. Set environment variables
export HCLOUD_TOKEN="your-hetzner-api-token"
export SOPS_AGE_KEY_FILE="./keys/age-key.txt"

# 2. Add client to terraform.tfvars
# clients = {
#   newclient = {
#     server_type = "cx22"
#     location    = "fsn1"
#     subdomain   = "newclient"
#     apps        = ["authentik", "nextcloud"]
#   }
# }

# 3. Deploy client (fully automated, ~10-15 minutes)
./scripts/deploy-client.sh newclient

The script will automatically:

  • Generate unique SSH key pair (if missing)
  • Create secrets file from template (if missing, opens in editor)
  • Provision VPS on Hetzner Cloud
  • Deploy Authentik (SSO/identity provider)
  • Deploy Nextcloud (file storage)
  • Configure OAuth2/OIDC integration
  • Set up SSL certificates
  • Create admin accounts

Result: Fully functional system, ready to use immediately!

Management Scripts

# Deploy a fresh client
./scripts/deploy-client.sh <client_name>

# Rebuild existing client (destroy + redeploy)
./scripts/rebuild-client.sh <client_name>

# Destroy client infrastructure
./scripts/destroy-client.sh <client_name>

See scripts/README.md for detailed documentation.

Manual Setup (Advanced)

Click to expand manual setup instructions
  1. Clone repository:

    git clone <repo-url>
    cd infrastructure
    
  2. Generate Age encryption key:

    age-keygen -o keys/age-key.txt
    # Store securely in password manager!
    
  3. Configure OpenTofu variables:

    cp tofu/terraform.tfvars.example tofu/terraform.tfvars
    # Edit with your Hetzner API token and configuration
    
  4. Create client secrets:

    cp secrets/clients/test.sops.yaml secrets/clients/<client>.sops.yaml
    sops secrets/clients/<client>.sops.yaml
    # Update client_name, domains, regenerate all passwords
    
  5. Provision infrastructure:

    cd tofu
    tofu init
    tofu apply
    
  6. Deploy applications:

    cd ../ansible
    export HCLOUD_TOKEN="your-token"
    export SOPS_AGE_KEY_FILE="../keys/age-key.txt"
    
    ansible-playbook -i hcloud.yml playbooks/setup.yml --limit <client>
    ansible-playbook -i hcloud.yml playbooks/deploy.yml --limit <client>
    

🎯 Project Principles

  1. EU/GDPR-first: European vendors and data residency
  2. Truly open source: Avoid source-available or restrictive licenses
  3. Client isolation: Full separation between tenants
  4. Infrastructure as Code: All changes via version control
  5. Security by default: Encryption, hardening, least privilege

📖 Documentation

🤝 Contributing

This project uses specialized AI agents for development:

  • Architect: High-level design decisions
  • Infrastructure: OpenTofu + Ansible implementation
  • Authentik: Identity provider and SSO configuration
  • Nextcloud: File sync/share configuration

See individual agent files in .claude/agents/ for responsibilities.

🔒 Security

  • Secrets are encrypted with SOPS + Age before committing
  • Age private keys are NEVER stored in this repository
  • See .gitignore for protected files

📝 License

TBD

🙋 Support

For issues or questions, please create a GitHub issue with the appropriate label:

  • agent:architect - Architecture/design questions
  • agent:infrastructure - IaC implementation
  • agent:authentik - Identity provider/SSO
  • agent:nextcloud - File sync/share