6 Commits

Include renames

Author	SHA1	Message	Date
Paul Nothaft	83a4344a01	fix: prevent database migration restart failures ... - Move migrations table insert inside PostgreSQL transaction for atomicity - Add PostgreSQL error codes 42701 (duplicate column), 42710 (duplicate object), and 23505 (unique violation) to error handling - Make migrations 006 and 008 idempotent with column existence checks Fixes #107	2026-01-15 15:43:13 +01:00
Claude	97589a7c5f	Fix issues #49 and #50: Migration errors and missing worker manager ... - Fix #49: Add column existence checks to migration 011_add_user_upload_settings.js to prevent "column already exists" errors during deployment - Fix #50: Create missing workerManager.js file that starts background services (file watcher and expiration checker) for native installations	2025-11-19 21:59:27 +00:00
paulandClaude	1b4b497fdf	chore: clean up codebase for production readiness ... - Remove all console.log/debug statements from production code - Add NODE_ENV checks for development-only logging - Remove test scripts (test-feedback, test-image-security, test-backup-*, test-restore) - Remove one-time fix scripts (fix-temp-photos, fix-migration-state, mark-migration-applied) - Remove sensitive files (.env.backup, ADMIN_CREDENTIALS.txt) - Update package.json to remove references to deleted scripts - Replace console statements with logger utility in backend - Secure error boundaries to not expose stack traces in production This makes the codebase production-ready with no debug output or test scripts. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>	2025-08-24 23:19:30 +02:00
paul	1cbeb75094	Fix migration column and JSON errors ... - Fixed migration 029: Use base email_templates columns (subject, body_html, body_text) instead of language-specific columns that don't exist yet - Fixed migration 004: JSON.stringify the setting_value for app_settings table - Removed German translations from backup email templates in core migration The errors occurred because: 1. Migration 029 assumed language columns existed, but they're added by later migrations 2. Migration 004 passed a plain string to a JSON column in PostgreSQL	2025-07-25 13:50:01 +02:00
paul	8a0a4436b0	Fix migration require paths after reorganization ... - Updated all core migrations to use ../../src/ instead of ../src/ - Updated legacy migrations with the same path fix - This fixes MODULE_NOT_FOUND errors during deployment The error occurred because migrations were moved one level deeper into core/ and legacy/ subdirectories without updating the relative paths to the source files.	2025-07-25 11:09:58 +02:00
paul	9854ca2f59	Reorganize migrations for new vs existing deployments ... - Created core/ directory for essential migrations that always run - Created legacy/ directory for migrations only needed when upgrading - New deployments will only run core migrations for a clean database - Existing deployments will run all migrations in proper sequence - Fixed duplicate migration numbers (014 and 027) - Updated migration runners to handle new directory structure - Added README explaining the migration organization This change optimizes deployment for new users who will get a clean schema without running unnecessary upgrade migrations.	2025-07-24 22:40:25 +02:00