How alphaqbit/ligtasalert_laravel- works
LigtasAlert is a Laravel emergency-alert application. Its primary workflow is that an operator or rescuee uses the web interface to submit an alert; the API controller validates and stores it, and operators can list, acknowledge, resolve, or add responders to alerts. The admin interface also requests alert statistics and facility data, while alert history supports review. The graph uses the sampled controllers, model, bootstrap, and admin view; route wiring and the other views are represented only where the tree supports their paths, so uncertain links are omitted.
Main entry points: api.php API routes · web.php Web routes · app.php App bootstrap · index.php HTTP entry
Components 17
Web entry
- HTTP entry
public/index.php - App bootstrap
bootstrap/app.php - Web routes
routes/web.php - API routes
routes/api.php
Alert API
- Alert operations
app/Http/Controllers/AlertController.php - Alert statistics
app/Http/Controllers/StatsController.php - Facility listing
app/Http/Controllers/FacilityController.php - Facility configuration
config/facilities.php
Alert domain
- Alert model
app/Models/Alert.php - Alert database
database/migrations/2026_09_25_000000_create_alerts_table.php - Database settings
config/database.php
User interfaces
- Admin dashboard
resources/views/admin.blade.php - Rescuee interface
resources/views/rescuee.blade.php - Debug view
resources/views/debug.blade.php
Other components
- Operator
- Rescuee
- Database
Connections 19
- Operator → HTTP entry: uses
- Rescuee → HTTP entry: uses
- HTTP entry → App bootstrap: boots
- App bootstrap → Web routes: loads routes
- App bootstrap → API routes: loads routes
- Web routes → Admin dashboard: serves
- Web routes → Rescuee interface: serves
- Web routes → Debug view: serves
- Admin dashboard → API routes: requests API
- Rescuee interface → API routes: requests API
- API routes → Alert operations: dispatches
- API routes → Alert statistics: dispatches
- API routes → Facility listing: dispatches
- Alert operations → Alert model: queries and updates
- Alert statistics → Alert model: counts alerts
- Facility listing → Facility configuration: reads
- Alert model → Alert database: persists alerts
- Alert database → Database: stored in
- Database settings → Database: configures