How mateusz-bogacz-collegiumwitelona/faily works
Faily is a Laravel application for organizing events and coordinating attendance and shared rides, with Vue/Leaflet map and event-form interfaces. The main web workflow takes event requests through EventController and EventService to the event repository and persistent models; the service also creates related rides and manages caching. Separate branches cover API access, registration, profiles, photos, reports, administration, and map/geocoding features. Several of these branches are visible in the file tree but were not sampled, so their internal links are omitted rather than inferred.
Main entry points: EventService.php Event service · EventRepository.php Event repository · EventController.php Event API · RideRequestController.php Ride request API
Components 21
Web experience
- Event form
src/resources/js/components/EventForm.vue - Map interface
src/resources/js/components/LeafletMap.vue - Web event actions
src/app/Http/Controllers/EventController.php
Events and rides
- Attendance workflow
src/app/Services/EventAttendeeService.php - Event service
src/app/Services/EventService.php - Event repository
src/app/Repositories/EventRepository.php - Event records
src/app/Models/Event.php - Ride sharing
src/app/Models/Ride.php - Ride requests
src/app/Http/Controllers/RideRequestController.php - Event photos
src/app/Models/Photo.php - Event cache
src/app/Services/CacheService.php
Identity and governance
- Registration
src/app/Http/Controllers/Auth/RegisteredUserController.php - Login sessions
src/app/Http/Controllers/Auth/AuthenticatedSessionController.php - Profile management
src/app/Http/Controllers/ProfileController.php - Locale middleware
src/app/Http/Middleware/SetLocale.php - Admin and reports
src/app/Http/Controllers/AdminController.php
API and maps
- Event API
src/app/Http/Controllers/Api/EventController.php - Ride request API
src/app/Http/Controllers/Api/RideRequestController.php - Map data and geocoding
src/app/Http/Controllers/MainMapController.php
Other components
- Visitor or member
- Application database
Connections 26
- Visitor or member → Web event actions: submits event
- Web event actions → Event service: calls
src/app/Http/Controllers/EventController.php - Event service → Event repository: queries and writes
src/app/Services/EventService.php - Event repository → Event records: uses records
src/app/Repositories/EventRepository.php - Event service → Ride sharing: creates ride
src/app/Services/EventService.php - Event service → Event photos: stores photos
src/app/Services/EventService.php - Event service → Event cache: uses cache
src/app/Services/EventService.php - Event repository → Application database: persists data
- Event records → Ride sharing: relates rides
src/app/Models/Event.php - Event form → Web event actions: submits form
- Visitor or member → Registration: registers
- Registration → Application database: creates account
src/app/Http/Controllers/Auth/RegisteredUserController.php - Visitor or member → Login sessions: signs in
- Login sessions → Application database: authenticates
- Visitor or member → Profile management: manages profile
- Visitor or member → Event API: uses API
- Event API → Event records: reads and writes
src/app/Http/Controllers/Api/EventController.php - Event API → Application database: queries records
src/app/Http/Controllers/Api/EventController.php - Visitor or member → Ride request API: requests ride
- Ride request API → Ride sharing: reads ride
src/app/Http/Controllers/Api/RideRequestController.php - Ride request API → Application database: queries records
- Visitor or member → Map interface: browses map
- Map interface → Map data and geocoding: loads map data
- Visitor or member → Attendance workflow: applies to event
- Attendance workflow → Application database: updates attendance
- Visitor or member → Admin and reports: administers platform