5 Commits

Author	SHA1	Message	Date
Claude	4e7e43c436	Implement PostgreSQL development parity and fix migration conflicts ... **PostgreSQL Development Setup:** - Update .env with PostgreSQL configuration options - Add comprehensive PostgreSQL setup guide (Docker + native) - Configure development-production database parity **Migration Conflict Resolution:** - Create fix_migrations command to handle Railway migration conflicts - Add reset_database command for clean development resets - Update Railway deployment with migration conflict handling - Add fake migration strategy for duplicate column errors **New Management Commands:** - `fix_migrations`: Diagnose and fix migration conflicts - `reset_database`: Clean reset of migrations and database - Support for both PostgreSQL and SQLite environments **Railway Deployment Fixes:** - Add migration conflict handling to railway.json - Use --fake-initial and --fake strategies for deployment - Better error recovery for existing schema conflicts **Developer Experience:** - Step-by-step PostgreSQL setup (Docker option for easy setup) - Migration troubleshooting guide - Development workflow documentation - Local-production environment matching **Fixes Railway Issue:** - Resolves "column data_file already exists" error - Handles existing database schema gracefully - Prevents future migration conflicts 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-12 09:59:44 +05:30
Claude	c8567e12cc	Fix Railway startup errors and add PostgreSQL setup guide ... **Fixed Railway Startup Issues:** - Reorder commands: migrate before backup_users - Make backup_users handle missing tables gracefully - Add proper error handling for unmigrated databases - Check for table existence before querying users **Added Railway Setup Guide:** - Complete PostgreSQL configuration instructions - Environment variables template - Database verification commands - Troubleshooting steps for persistent storage **Key Issue Resolution:** - Railway using SQLite (ephemeral) instead of PostgreSQL - Users disappear because SQLite resets on each deployment - Need to add PostgreSQL database addon in Railway **Next Steps:** 1. Add PostgreSQL database in Railway dashboard 2. Verify DATABASE_URL environment variable 3. Deploy with persistent database 4. Create admin user via Railway console 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-12 09:16:39 +05:30
Claude	362e877ee1	Fix Railway database persistence and admin user issues ... **Database Management Improvements:** - Fix populate_agents to not overwrite existing admin users - Add --create-admin flag for explicit admin creation - Check if admin email exists before creating new admin - Better logging of superuser status **New Management Commands:** - backup_users: Backup/restore user data and wallet transactions - create_user: Create users with initial wallet balance - Both commands help recover from data loss issues **Railway Configuration:** - Add database info display on deployment - Better handling of existing user data - Prevents admin password resets on every deploy **Fixes:** - Admin password no longer resets to 'admin123' on every deployment - User data should persist between Railway deployments - Better debugging tools for database issues 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-12 09:12:16 +05:30
Claude	9aa144faf8	Add database population for Railway deployment ... - Create populate_agents management command to add default agents - Add admin user creation (admin@netcop.ai / admin123) - Update Railway startup to run population after migrations - This fixes empty marketplace and login issues on Railway 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-12 05:11:08 +05:30
Claude	4d2d19f79f	Add Railway deployment config	2025-07-12 03:43:14 +05:30