Paul Nothaft
9872ad3aef
Addresses GitHub issue #132 - enables filtering client feedback and exporting filenames for use in Lightroom. Changes: - Add original_filename column to photos table via migration - Store original filename during photo upload - Fix export service column name mismatches (path, size_bytes, uploaded_at) - Fix table name (photo_categories instead of categories) - Fix toFixed() calls to handle string ratings from database Export formats available: - TXT with comma separator (for Lightroom Library Filter) - CSV with full metadata - JSON for automation - XMP sidecar files (for Lightroom/Bridge/Capture One)
Database Migrations
This directory contains database migrations for the PicPeak photo sharing platform.
Directory Structure
/core
Essential migrations that are always run for new deployments. These include:
init.js- Initial database schema creation- Backup service tables (029-035)
- Gallery feedback tables (033)
- Pre-generated watermarks (061)
/legacy
Migrations needed only when upgrading from older versions. New deployments can skip these as the core schema already includes all necessary tables and columns.
For New Deployments
If you're deploying this application for the first time:
- The
initializeDatabase()function insrc/database/db.jswill create all necessary tables - Only migrations in the
/coredirectory will be run - This ensures a clean, optimized database schema
For Existing Deployments
If you're upgrading from an older version:
- All migrations (both core and legacy) will be run in sequence
- The migration system tracks which migrations have been applied
- Only new migrations will be executed
Running Migrations
# Development
npm run migrate
# Production
npm run migrate:prod
Note on Duplicate Migration Numbers
The legacy directory contains renamed duplicates:
014_add_host_name_to_events_duplicate.js(was duplicate of 014)027_add_rate_limit_settings_duplicate.js(was duplicate of 027)
These have been renamed to avoid conflicts while preserving the migration history.