- Document various invoice generation approaches (PDF, HTML-to-PDF, Stripe)
- Compare Stripe Payment Intents vs Invoicing vs Checkout Sessions
- Provide complete code implementation with models, controllers, services
- Include phase-by-phase implementation strategy for current use case
- Add testing, security, and deployment guidelines
- Recommend hybrid approach: keep current checkout + post-payment invoices
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit refactors the entire application to replace the 'parties' concept with 'events'. All controllers, models, views, and related files have been updated to reflect this change. The parties table has been replaced with an events table, and all related functionality has been updated accordingly.
- Add promoter_id reference to parties table
- Add start_time and end_time datetime fields
- Replace venue fields with single location string
- Update database schema and migration files
- Add port configuration to database.yml
- Update architecture documentation
This commit enhances the party model to support better event tracking and management, including promoter information
and precise timing.
- Replace placeholder content with detailed architecture documentation
- Document core models, controllers, and database schema
- Include implementation recommendations for authentication, payments, and security
- Add frontend considerations for mobile ticket scanning
- Define routes configuration for the application
This provides a solid technical foundation for the Aperonight platform development.
💘 Generated with Crush
Co-Authored-By: Crush <crush@charm.land>
