Lumina Documentation

LuminaAI Installation Guide (Laravel + Livewire + Filament)

Choose the section you need. This documentation is split into focused pages for faster onboarding.

Lumina Docs HomeDocs Index

Overview

This guide covers full installation for the Lumina project, including local development and production deployment. Use the focused pages below for exact commands and platform onboarding.

Local Setup

XAMPP/WAMP/Laragon + Composer + Node + migrations + assets.

VPS Deployment

Ubuntu + Nginx + PHP-FPM + Redis + Supervisor + hardening.

Shared Hosting

cPanel/Plesk constraints, docroot, cron, queue fallbacks.

API Providers

Step-by-step registration and key retrieval from .env.example platforms.

Documentation Paths

  • Public route: https://somatechglobalventures.com/documentation/lumina-project

Quick Start (Local)

  1. Install PHP 8.2+, Composer 2, Node 20, MySQL, and Redis (optional for local).
  2. Clone project, copy .env.example to .env.
  3. Run migrations/seeders and build front-end assets.
  4. Open app and complete admin/payment/API settings.

Pre-Launch Checklist (Copy/Paste Ready)

Use this final checklist before production release. Mark each item as done.

Application and Environment

  • [ ] APP_ENV=production and APP_DEBUG=false are set.
  • [ ] APP_URL uses your HTTPS domain (no localhost values).
  • [ ] APP_KEY exists and is not empty.
  • [ ] Required API/payment/provider keys are set and verified.

Database and Admin Access

  • [ ] Production DB exists and credentials in .env are correct.
  • [ ] Latest migrations ran successfully.
  • [ ] Seed/admin user was created and can log in to Filament.
  • [ ] Admin route is reachable (usually /admin).

Domain, SSL, and Email

  • [ ] Domain DNS points to hosting/VPS correctly.
  • [ ] SSL certificate is active and auto-renew enabled.
  • [ ] Site loads with HTTPS only (no mixed content warnings).
  • [ ] SMTP credentials are correct and test emails are delivered.

Performance and Operations

  • [ ] Caches compiled: config, routes, views.
  • [ ] storage and bootstrap/cache are writable.
  • [ ] Queue worker is running (Supervisor/systemd/hosting fallback).
  • [ ] Scheduler cron is active and tested.
  • [ ] Monitoring/log review path is confirmed for incident debugging.

Post-Launch Verification (First 24 Hours)

Run this checklist after deployment to confirm production stability and service health.

Traffic, Access, and Security

  • [ ] Homepage and critical pages load from multiple devices/networks.
  • [ ] Admin panel login/logout works normally.
  • [ ] HTTPS redirect is always enforced and certificate is valid.
  • [ ] No unexpected public access to internal/admin-only routes.

Application Health and Logs

  • [ ] Review Laravel logs for new errors/warnings every few hours.
  • [ ] Monitor web server logs (Nginx/Apache) for spikes in 4xx/5xx.
  • [ ] Verify no repeated fatal exceptions or memory exhaustion events.
  • [ ] Confirm storage disk usage is stable and not unexpectedly growing.

Queue, Scheduler, and Jobs

  • [ ] Queue workers are running and processing jobs continuously.
  • [ ] Failed jobs table remains empty or failures are investigated immediately.
  • [ ] Scheduled tasks execute on time (emails, reports, maintenance tasks).
  • [ ] Horizon/Supervisor/PM2 services auto-restart after reboot.

Data, Email, and Recovery Readiness

  • [ ] New records are saved correctly and visible in admin lists.
  • [ ] Outbound SMTP emails are delivered (test to Gmail/Outlook/custom domain).
  • [ ] Backup strategy is active (DB dump + files) and restore drill is documented.
  • [ ] Team has rollback steps ready (previous build, env backup, DB restore plan).

Emergency Runbook (Rapid Incident Response)

Use this runbook during production incidents. Follow top to bottom and record all actions taken.

0) First 5 Minutes (Always Do This First)

  • [ ] Confirm incident scope: all users, specific pages, or admin-only failure.
  • [ ] Pause deployments and config changes until root cause is identified.
  • [ ] Check host/VPS status, CPU/RAM/disk, and recent deploy timeline.
  • [ ] Tail Laravel + web server logs and capture first critical error.

1) Site Down (5xx / White Screen / 502-504)

  • [ ] Run: php artisan optimize:clear and re-test health URL.
  • [ ] Restart runtime services: Nginx/Apache, PHP-FPM, queue workers.
  • [ ] Validate .env values and ensure APP_KEY is present.
  • [ ] If still down, roll back to last known good release immediately.

2) Database Outage or Connection Failures

  • [ ] Verify DB service status and active connections.
  • [ ] Confirm DB host/user/password/database in .env.
  • [ ] Check for full disk or table corruption warnings.
  • [ ] Restore latest clean backup if corruption is confirmed.

3) SSL Expired or HTTPS Broken

  • [ ] Check certificate expiry date and DNS A/AAAA records.
  • [ ] Reissue/renew SSL (AutoSSL/Certbot) and reload web server.
  • [ ] Confirm HTTPS redirect and remove mixed-content asset URLs.
  • [ ] Keep HTTP fallback only temporarily if business-critical.

4) Queue Stuck / Scheduler Not Running

  • [ ] Restart supervisor/Horizon/workers and inspect failed jobs.
  • [ ] Re-run critical failed jobs after fixing root cause.
  • [ ] Verify cron entry for scheduler uses correct project path.
  • [ ] Add temporary monitoring alert for queue lag and failures.

5) SMTP/Email Delivery Outage

  • [ ] Verify SMTP credentials, port, encryption, and auth settings.
  • [ ] Confirm mailbox quota, SPF, DKIM, and DMARC records.
  • [ ] Send test mail from app and provider console, compare logs.
  • [ ] Switch to backup SMTP provider if primary is unavailable.

6) Recovery Completion and Follow-up

  • [ ] Confirm app, admin, queue, scheduler, DB, and email are stable.
  • [ ] Document root cause, exact fix, and prevention actions.
  • [ ] Create monitoring/alert rule for the failure signature.
  • [ ] Share incident summary with timeline and customer impact.