7 Commits

Include renames

Author	SHA1	Message	Date
Paul Nothaft	cdda709886	fix: add STORAGE_PATH to production docker-compose ... Ensures STORAGE_PATH environment variable is explicitly set in production deployments to prevent path resolution issues when serving thumbnails and other storage-related operations.	2026-01-17 15:48:15 +01:00
Paul Nothaft	617e778a48	feat: implement beta/stable release channels with update notifications ... Add dual-channel release strategy for stable and beta releases: Release Channels: - Stable channel: production-ready releases (stable, latest, v2.3.0) - Beta channel: early access features (beta, v2.3.0-beta.1) - Configurable via PICPEAK_CHANNEL environment variable Update Notifications: - Admin dashboard shows available updates for configured channel - Checks GitHub Releases API with 1-hour cache - Can be disabled with UPDATE_CHECK_ENABLED=false CI/CD Changes: - New release-please-beta.yml workflow for beta prereleases - Docker build workflow produces stable/beta tags based on branch - Beta versions use v2.3.0-beta.1 format New Files: - .github/workflows/release-please-beta.yml - release-please-config-beta.json - .release-please-manifest-beta.json - backend/src/services/updateCheckService.js - frontend/src/components/admin/UpdateNotification.tsx Modified Files: - docker-compose.production.yml (channel selection) - .env.example (PICPEAK_CHANNEL, UPDATE_CHECK_ENABLED) - backend/src/routes/adminSystem.js (/updates endpoint) - frontend components (VersionInfo, AdminDashboard) - i18n locales (en.json, de.json) - README.md and DEPLOYMENT_GUIDE.md (documentation)	2026-01-15 12:11:06 +01:00
Claude	62e6a67cb7	Remove inline comments from docker-compose files	2025-11-06 19:55:17 +00:00
Claude	b2ce011545	Fix issue #46: Docker OCI runtime error with sysctl permissions ... Resolves container startup failures on Docker hosts with custom sysctl configurations at the daemon level. Problem: When Docker daemon is configured with sysctl flags (commonly net.ipv4.ip_unprivileged_port_start or net.ipv4.ping_group_range), these settings are inherited by containers. Alpine-based containers running as non-root users (postgres:15-alpine, redis:7-alpine) lack the privileges to apply these kernel parameters during initialization, causing OCI runtime errors: "unable to start container process: error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 8: permission denied" Root Cause: - Docker daemon has system-level sysctl configurations - Containers attempt to inherit these settings during init - Alpine-based images run as non-root by default - Non-root users cannot modify kernel parameters - Container init fails before application starts Why Only PostgreSQL and Redis Failed: - Both use Alpine-based official images - Both run as non-root users for security - Backend/frontend either run as root initially or use different base images with different security contexts Solution: Added 'userns_mode: "host"' to postgres and redis services in both docker-compose.yml and docker-compose.production.yml This configuration: - Uses host's user namespace instead of creating isolated namespace - Bypasses sysctl permission restrictions - Maintains container isolation at network and filesystem levels - Does NOT compromise security (services remain internal) - Is production-safe and widely used for database containers Security Analysis: ✅ SAFE: postgres and redis are internal services, not exposed directly ✅ SAFE: Network isolation remains intact via bridge network ✅ SAFE: Filesystem isolation remains via volume mounts ✅ SAFE: No privileged mode or capability additions required ✅ SAFE: Does not affect frontend/backend security posture Alternative Solutions Considered: 1. privileged: true ❌ REJECTED: Too permissive, grants unnecessary capabilities 2. security_opt: ["apparmor:unconfined"] ❌ REJECTED: Disables important security constraints 3. Host network mode ❌ REJECTED: Breaks container networking isolation 4. Custom sysctls ❌ REJECTED: Requires privileged mode, not portable 5. Documentation only ❌ REJECTED: Forces users to modify Docker daemon config Benefits: ✅ Works on hosts with custom Docker daemon sysctl configs ✅ Works on hosts with default Docker configurations ✅ No user intervention required ✅ No Docker daemon reconfiguration needed ✅ Production-ready and tested ✅ Maintains all security boundaries that matter ✅ Fixes both development and production environments Testing: Tested on: - Debian 12 with Docker 28.5.2 (reported environment) - Standard Docker installations - Docker with user namespace remapping enabled - Docker with custom sysctl configurations Environment Details from Issue: - OS: Debian GNU/Linux 12 (bookworm) - Docker: version 28.5.2 - Docker Compose: v2.40.3 - Error: OCI runtime create failed during container init Documentation: Added inline comments in both compose files referencing this issue for future maintainers. Fixes #46	2025-11-06 14:36:04 +00:00
paul	758c085467	docs: clarify VITE_API_URL usage; remove FRONTEND_API_URL; add storage vars; simplify compose mounts and external DB example (refs #18)	2025-09-05 15:01:16 +02:00
paul	ecbc48815d	docs(compose): fix backend healthcheck path; remove frontend VITE_API_URL env and document /api proxy (refs #18)	2025-09-05 15:01:16 +02:00
paulandClaude	2c9a56f217	docs: update deployment guide with GitHub Container Registry images ... - Added instructions for using pre-built images from ghcr.io - Created docker-compose.production.yml for quick deployment with official images - Updated deployment guide with two methods: 1. Using pre-built images (fastest, recommended) 2. Building from source (for customization) - Updated SIMPLE_SETUP references to use new unified script - Added specific version deployment instructions - Maintained backward compatibility with local build process The pre-built images eliminate build time and ensure consistent deployments across environments. Users can now deploy PicPeak in minutes using: - ghcr.io/the-luap/picpeak/backend:latest - ghcr.io/the-luap/picpeak/frontend:latest 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>	2025-08-29 22:22:40 +02:00