8 Commits

Include renames

Author	SHA1	Message	Date
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	8d85454ef6	Make credential file writing optional in migration ... - Wrapped file writing in try-catch to prevent migration failure - Credentials are always shown in console output - File writing is now optional - if it fails, migration continues - Added informative message when file cannot be written This prevents the migration from failing in environments where the data directory has permission issues, while still ensuring administrators can see and copy the credentials from console output.	2025-07-25 13:29:02 +02:00
paul	596bba2c1b	Fix permission error when writing admin credentials ... - Changed credential file location from /app/ to /app/data/ - Added directory creation with recursive flag - Updated console messages to show correct file location - The data/ directory is already owned by nodejs user in Dockerfile The error occurred because the nodejs user doesn't have write permission to /app/ directory, but does have permission to /app/data/ which is explicitly created and chowned in the Dockerfile.	2025-07-25 13:20:44 +02:00
paul	055de06315	Fix 001_init.js database column mismatch ... - Removed must_change_password field that doesn't exist in admin_users table - Changed from using db to knex parameter for database operations - Fixed require statement that was accidentally changed - Updated security message to reflect no forced password change - Removed debug logging after identifying the issue The error occurred because 001_init.js was trying to insert a column that doesn't exist in the admin_users table schema created by initializeDatabase().	2025-07-25 13:15:06 +02:00
paul	ccf59d1d4d	Fix 001_init.js to follow proper migration pattern ... - Changed from standalone script to proper migration with exports.up/down - Removed process.exit() calls that were terminating the migration runner - Removed immediate execution of runMigrations() - Now properly exports migration functions like other migrations This was the root cause - 001_init.js was executing immediately when required and calling process.exit(), preventing it from being run as a migration and causing 029 to run first on an empty database.	2025-07-25 13:00:03 +02:00
paul	519518ed6c	Fix migration order by renaming init.js to 001_init.js ... - Renamed core/init.js to core/001_init.js to ensure it runs first - Updated detectExistingSchema() to reference 001_init.js - This fixes the issue where backup migrations tried to access app_settings table before it was created - Migrations now run in correct order: init first, then numbered The error occurred because alphabetical sorting put 029 before init, causing migrations to fail on new deployments.	2025-07-25 11:37:52 +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