How ptlc8/events works
Main Components
a. Client Layer:
• Web Frontend (Vue.js PWA)
• Mobile App (Android/Capacitor)
b. API Layer:
• PHP Backend API
• Event-related endpoints (/events/*)
• User-related endpoints (/users/*)
• Image handling endpoints (/images/*)
c. Data Layer:
• MariaDB Database
• Event data storage
• User data storage
d. External Services:
• Mapbox (for maps)
• Portal Authentication System
• SeatGeek API
• Ticketmaster API
• OpenAgenda
• DataTourisme
Component Relationships
• Frontend → API (REST calls)
• API → Database (data persistence)
• API → External Services (third-party integrations)
• Aggregation Service → Database (event data population)
Key Architectural Elements
a. Frontend Architecture:
• Vue.js Components
• Stores (Vuex/Pinia)
• Router
• PWA capabilities
b. Backend Architecture:
• PHP API endpoints
• Authentication middleware
• Event aggregation system
Clear separation between these components
Deployment View
Docker containers for:
• Frontend container
• API container
• Database container
• Aggregation container
External Services Layer
Important Notes:
• Data flow for key operations (event search, user authentication, etc.)
• Aggregation system as it's a crucial component
• Which components are containerized
• Environment variable dependencies
• Version information for key components (PHP 8, MariaDB)