NexusLMS Documentation

Introduction

NexusLMS is a corporate training platform: a Laravel backend with an admin panel and a learner web portal, a REST API, and a Flutter mobile app for iOS and Android. Admins build courses, quizzes and assignments and assign them to departments; employees learn in the browser or on their phone.

This documentation is for version 1.0.0. It is a single page that opens offline from the documentation folder.

It is also online, always in its latest version, at shamimcse1.github.io/nexuslms-docs. Use the search box at the top of the menu (or press /) to find any topic.

Want to look around first? Open the live demo's admin panel or learner portal, or install the Android demo app. The demo’s data resets every 15 minutes.
Admin: admin@nexuslms.internal / Admin@123456
Learner (portal and app): employee@corporation.com / Password@123
All demo accounts are in Demo Instructions.

What's in the package

FolderWhat it is
main/backend/Laravel application: admin panel, learner portal, REST API and web installer (Laravel 13, PHP 8.3+).
main/mobile/Flutter app for learners (Android and iOS).
documentation/This documentation and its screenshots (assets/).

The backend comes without the folders Composer and npm create (vendor/, node_modules/ and public/build/), and the app without Flutter's build/ folder. The first setup steps add them.

Quick start

Setting up takes five steps. Click a step to jump to its instructions.

  1. Install the backendInstall the PHP packages, build the web assets, upload the files and run the web installer.
  2. Set up the admin panelSign in, set your site name, logo and time zone, then add departments, people and courses.
  3. Connect emailA mail server is needed for password resets. Push notifications are optional.
  4. Build the mobile appSet your API address, rename the app, change the icon and build it.
  5. Go liveWork through the going-live checklist before inviting people.

Requirements

Demo Instructions

Try NexusLMS before you install it. The demo resets its sample data every 15 minutes and does not send email.

Demo logins

AccountSign in atEmailPassword
Super AdminAdmin paneladmin@nexuslms.internalAdmin@123456
Company AdminAdmin paneladmin@corporation.comAdmin@123456
LearnerLearner portal and Android appemployee@corporation.comPassword@123

The sign-in pages also list these accounts; click one to fill it in. These logins are for the online demo only. On your own installation, sign in with the administrator you create in the installer.

Backend & admin panel

The backend in main/backend is a Laravel 13 application. It serves the admin panel at /admin, the learner portal at /portal, the REST API at /api/v1 and the web installer at /install.

Installation

  1. Upload the contents of main/backend to your server, for example to /var/www/nexuslms.
  2. Point your domain's document root to the public folder inside it.
  3. Install the PHP packages:
    cd /var/www/nexuslms
    composer install --no-dev --optimize-autoloader
  4. Build the web assets (CSS and JavaScript):
    npm ci
    npm run build
  5. Make the storage and cache folders writable by the web server:
    chmod -R 775 storage bootstrap/cache
    chown -R www-data:www-data storage bootstrap/cache
    (Use your web server's user instead of www-data if it differs.)
  6. Create an empty MySQL database and a database user with full access to it.
  7. Open https://your-domain.com/install in your browser and follow the web installer.

Web installer

  1. Requirements: checks the PHP version, extensions and folder permissions. Fix anything marked red before continuing.
  2. Database: enter the database host, port, name, user and password. The installer tests the connection and saves it to .env.
  3. Migrate: creates the database tables. The Import demo data option adds sample courses, learners and content. Leave it off on a live site: the sample accounts have default passwords that are the same on every installation.
  4. Administrator: choose the site name, URL and your own administrator name, email and password.
  5. Finish: the installer switches the site to production mode (APP_ENV=production, APP_DEBUG=false), links the public storage folder and locks itself. Sign in at /admin.
Installer step 1 checks the PHP version, extensions and folder permissions.
Figure 1: Installer step 1 checks the PHP version, extensions and folder permissions.
Installer step 2: enter your database connection details.
Figure 2: Installer step 2: enter your database connection details.
Installer step 3 creates the tables. Leave demo data off on a live site.
Figure 3: Installer step 3 creates the tables. Leave demo data off on a live site.
Installer step 4: choose the site name and your own administrator account.
Figure 4: Installer step 4: choose the site name and your own administrator account.
The installer finishes, switches to production mode and locks itself.
Figure 5: The installer finishes, switches to production mode and locks itself.
The admin sign-in page at /admin.
Figure 6: The admin sign-in page at /admin.
If you imported demo data, change the passwords of the sample accounts (or delete them) under Admin → Users before inviting real learners.

For a public demo site only, set DEMO_MODE=true in .env to show the sample sign-in accounts on the login pages. It is off by default.

Scheduler (cron)

Live class reminders (every 5 minutes), due date and certificate expiry reminders (once a day at 08:00) and the weekly cleanup of replaced assignment files run through the Laravel scheduler. Add this single cron entry on your server:

* * * * * cd /var/www/nexuslms && php artisan schedule:run >> /dev/null 2>&1

Everything else works without it. No queue worker is required: push notifications and emails are sent right after each request finishes.

Email

Password reset emails need a working mail server. Set these values in .env (your provider gives you them):

MAIL_MAILER=smtp
MAIL_HOST=smtp.your-provider.com
MAIL_PORT=587
MAIL_USERNAME=your-username
MAIL_PASSWORD=your-password
MAIL_SCHEME=smtp
MAIL_FROM_ADDRESS="learning@your-company.com"

MAIL_SCHEME=smtp uses STARTTLS, usually on port 587. For SSL on port 465, set MAIL_SCHEME=smtps and MAIL_PORT=465.

You can also enter these in Admin → Settings → SMTP Email Server. Values saved there are used instead of the .env values; leave the host empty to keep using .env. Send Test Email sends a real email and shows the mail server's error if it fails.

SMTP settings
Figure 7: SMTP settings in Admin → Settings.

The reset link opens /portal/reset-password, where learners choose a new password. It works for both the portal and the mobile app.

Local testing and demo mode

To try NexusLMS on your own computer:

cp .env.example .env
composer install
npm install && npm run build
php artisan key:generate
php artisan serve

Create an empty database, open http://127.0.0.1:8000/install and tick Import demo data in step 3 to get sample courses and the demo accounts. The installer switches the site to production mode; for local debugging set APP_DEBUG=true in .env afterwards. Set DEMO_MODE=true to show the demo accounts on the sign-in pages (only for a public demo site).

Going-live checklist

Updating to a new version

  1. Back up your database and the .env file and storage folder.
  2. Upload the new files, keeping your .env and storage folder.
  3. Run:
    composer install --no-dev --optimize-autoloader
    npm ci && npm run build
    php artisan migrate --force
    php artisan optimize:clear

Admin panel

Sign in at /admin with the administrator account you created in the installer.

SectionWhat you can do
DashboardSee enrollment, completion and activity at a glance.
CoursesCreate courses with modules and lessons (video, PDF, formatted text or external links), set completion rules, prerequisite gates, drip schedule and certificate expiry, and publish them. Video uploads (MP4, M4V, WebM, MOV up to 100 MB) or YouTube/Vimeo embeds stream with dynamic learner watermarks; PDF documents open in a secure viewer.
QuizzesBuild assessments with multiple-choice, true/false and short-answer questions, a time limit, a pass mark and an attempt limit. Short-answer questions are left out of the automatic score until an instructor marks them: open the quiz's attempts, click Needs review, award points and optional feedback. The score and pass result are then recalculated and the learner is notified.
AssignmentsAdd assignments to a course with allowed file types, a size limit and a deadline. Review and grade submissions; learners are notified.
Learning pathsGroup courses into a path and assign it to people or whole departments.
Live classesSchedule sessions with a meeting link (Zoom, Teams, Google Meet). Learners can join from 15 minutes before the start; a reminder is sent automatically. Add the recording link afterwards.
CertificatesIssue, revoke and verify certificates and edit certificate templates.
Departments and usersManage departments, employees and their course assignments.
RolesTick the permissions each role has (for example View users, Grade assignments, Edit settings). Changes apply immediately. You can also create your own roles. Only a Super Admin can open this page. See Who can open what.
NotificationsSend announcements to everyone, a department, a course or one person, and edit the emails the platform sends: account welcome, course assigned, course completed, certificate issued, live class invitation and due date reminder. Switch a template off to stop that email. Send Test Email emails the template to you with sample values.
ReportsTrack compliance and course progress, export reports, and send a reminder to a learner with one click. Learners also get automatic reminders 14, 7 and 1 days before a due date, and before a certificate expires.
SettingsSite and company name, logo and favicon, email (SMTP), Firebase push, time zone, session timeout and due date reminders, and the privacy policy and help desk details.
The admin dashboard.
Figure 8: The admin dashboard.
Course list
Figure 9: Courses & Curricula: every course with its status.
The curriculum builder: modules and lessons for one course.
Figure 10: The curriculum builder: modules and lessons for one course.
The quiz builder: questions, options and the correct answers.
Figure 11: The quiz builder: questions, options and the correct answers.
Assignment submissions, ready for grading.
Figure 12: Assignment submissions, ready for grading.
Reports
Figure 13: Compliance & Reports, with export.

Settings

Open Admin → Settings to set up the platform. Each tab is shown below.

General settings
Figure 14: General & Branding: site name, company, logo and favicon.
Time zone setting
Figure 15: Time Zone: the time zone used for dates and times across the platform.
Firebase settings
Figure 16: Firebase & Push: optional push notifications (see Push notifications).
Security settings
Figure 17: Security & Compliance: session timeout, automatic due date reminders and a server summary.
Privacy and support settings
Figure 18: Privacy & Support: IT Help Desk contacts and the privacy policy.

Privacy & Support holds the IT Help Desk details (email, phone, help center link and support hours) and your privacy policy. In the mobile app, IT Help Desk on the sign-in screen lists the contacts you fill in, and Privacy Policy opens the policy inside the app. The policy is also published at https://your-domain.com/privacy-policy, which you can use as the privacy policy link in the App Store and Google Play. Until you write your own, a starter policy is shown; it fills in your company name automatically. You can paste plain text or simple HTML (headings, paragraphs, lists and links).

Who can open what

Each admin page needs a permission, and each role holds a set of permissions that you can change under Admin → Roles & Permissions. A Super Admin always has every permission. The defaults are:

RoleDefault access
Super AdminEverything, including Roles & Permissions.
Company AdminEverything except Roles & Permissions. Cannot create, edit or delete Super Admin accounts.
ManagerView users, manage departments, view courses and assign them, learning paths, view certificates and live classes, reports (view, export, reminders) and announcements.
InstructorCreate and edit courses, quizzes (including short-answer review), grade assignments, host live classes and take attendance, view reports.
EmployeeThe learner portal and mobile app only, and only the courses they are enrolled in (or courses that allow self-enrollment).

A role you create yourself can open the admin panel as soon as it has at least one permission. Giving permissions to the Employee role lets every learner into the admin panel, so leave it empty.

Lesson files and assignment submissions are stored privately in storage/app/private. Learners reach them only through authenticated stream and download routes that verify active course enrollment on every request.

First-time setup

  1. Settings → General & Branding: site and company name, logo and favicon.
  2. Settings → Time Zone: choose your time zone before you schedule live classes or set due dates.
  3. Settings → SMTP Email Server: mail settings, then send a test email.
  4. Departments, then Users: add people one by one or import a CSV file (download the sample from the Users page). Each imported person is emailed a link to choose their own password, so set up email first; anyone who misses it can use Forgot password on the sign-in page.
  5. Courses: create a course, add modules and lessons, add quizzes and assignments, publish it and assign it to departments or people.

Demo credentials

Demo accounts exist only if you tick Import demo data in the installer. The administrator you create in the installer is separate and uses your own password.

AccountSigns in atEmail
Super Admin/adminadmin@nexuslms.internal
Company Admin/adminadmin@corporation.com
Manager/adminmanager@corporation.com
Instructor/admininstructor@corporation.com
Learner/portal and the appemployee@corporation.com

To try them, set DEMO_MODE=true in .env: the admin sign-in page then offers the Super Admin and Company Admin accounts, and the portal sign-in page the Learner account, with their passwords filled in. The Manager and Instructor accounts use the same password as the Learner.

On a live site, leave DEMO_MODE off and delete the demo accounts or give them new passwords under Admin → Users.

White-labeling

Learner portal

Employees sign in at /portal to see their assigned courses, continue lessons, take quizzes, submit assignments, join live classes, and view and print certificates. The site root (/) opens the portal.

The learner portal dashboard.
Figure 19: The learner portal dashboard.
Course overview
Figure 20: A course in the portal: progress, curriculum, quizzes and assignments.
Course player
Figure 21: The course player, showing a text lesson with the curriculum alongside.
Forgot password
Figure 22: Learners can reset a forgotten password from the sign-in page.

Architecture

PathPurpose
app/Http/Controllers/AdminAdmin panel pages.
app/Http/Controllers/PortalLearner web portal.
app/Http/Controllers/Api/V1REST API used by the mobile app.
app/Http/Controllers/InstallController.php, app/Services/InstallService.phpWeb installer.
app/Http/MiddlewareAdmin access, the permission each admin page needs (AdminPermission), and the installer lock.
app/ModelsDatabase models.
app/ServicesCourse progress, notifications and push (LearnerNotifier, FirebaseService), short-answer review (QuizAttemptReviewer) and safe lesson text (RichText).
app/Console/CommandsLive class reminders, due date and certificate expiry reminders, and cleanup of replaced assignment files.
database/migrations, database/seedersTables, default roles, permissions and email templates; demo data.
resources/views/admin, portal, installBlade templates.
routes/web.php, routes/api.php, routes/console.phpWeb pages, API and scheduled tasks.
storage/app/privateLesson files and assignment submissions (not publicly reachable).

Key design decisions

API

The mobile app uses the API at https://your-domain.com/api/v1. Learners sign in with POST /api/v1/auth/login and receive a bearer token, which is sent as Authorization: Bearer <token> on every other request. Sign-in and password reset requests are rate limited.

Signed-in requests are limited to 120 per minute; sign-in to 5 attempts per minute.

AreaEndpoints (all under /api/v1/)
Sign-in and accountPOST auth/login, auth/logout, auth/forgot-password, auth/reset-password, GET auth/me
HomeGET dashboard, GET system/config
Courses and lessonsGET courses, courses/{slug}, courses/{slug}/lessons/{id}, โ€ฆ/stream, POST โ€ฆ/complete
Learning pathsGET learning-paths, learning-paths/{slug}
QuizzesGET quizzes/{id}, POST quizzes/{id}/start, quizzes/{id}/submit, GET quizzes/{id}/attempts/{attempt}
AssignmentsGET assignments, assignments/{id}, POST assignments/{id}/submit (file upload)
Live classesGET live-classes, POST live-classes/{id}/join
CertificatesGET certificates, certificates/{number}
NotificationsGET notifications, POST notifications/{id}/read, notifications/read-all, POST device-token
ProfileGET profile, POST profile (photo), POST profile/change-password

Tests

The backend has 320 automated tests. They run on an in-memory SQLite database, so no MySQL is needed (PHP's pdo_sqlite extension must be enabled):

php artisan test

They cover the installer, sign-in and password reset, roles and permissions, enrollment checks, courses and lessons, quizzes and short-answer review, assignments, live classes, certificates, notifications and push, and the API.

The mobile app has 189 tests, including an architecture test that keeps the code layered:

flutter analyze
flutter test

Mobile app: setup and running

  1. Open main/mobile in Android Studio or VS Code.
  2. Create your settings file from the example and set your API address:
    cp assets/.env.example assets/.env
    API_BASE_URL=https://your-domain.com/api/v1
    If assets/.env is missing, the app uses the values in assets/.env.example. To try the app before your server is ready, set API_BASE_URL=https://nexuslms.dev-shamim.com/api/v1 and sign in with the demo learner account from the item description.

    Set API_BASE_URL to your server's address followed by /api/v1:

    • Live server: https://your-domain.com/api/v1 (use HTTPS; Android blocks plain HTTP in release builds).
    • Android emulator with a server on your computer: http://10.0.2.2:8000/api/v1.
    • iOS simulator with a server on your computer: http://127.0.0.1:8000/api/v1.

    After changing it, stop the app and run it again; a hot reload does not pick up .env changes.

    API_BASE_URL in assets/.env.example in Android Studio
    Figure 23: The API address is the API_BASE_URL line in the assets folder's .env file.
  3. Install packages and run:
    flutter pub get
    flutter run

What the app looks like

Sign in with a learner account.
Figure 24: Sign in with a learner account.
Home: progress, live classes and assigned courses.
Figure 25: Home: progress, live classes and assigned courses.
Course details and progress.
Figure 26: Course details and progress.
Certificates, with a public verification link.
Figure 27: Certificates, with a public verification link.
Live classes and past recordings.
Figure 28: Live classes and past recordings.
Notifications, grouped by day.
Figure 29: Notifications, grouped by day.

Testing on a real phone

On a phone on the same Wi-Fi as your computer, use your computer's network address, for example http://192.0.2.10:8000/api/v1, and start Laravel with php artisan serve --host=0.0.0.0. Plain http:// works only in debug builds; release builds need https://.

File structure

The app in main/mobile is organized by feature. Each feature has the same three layers, so once you know one feature you can find your way around all of them.

PathPurpose
lib/main.dartStarts the app: loads assets/.env, sets up Firebase when it is configured, and runs app.dart.
lib/app.dartThe root widget: theme, the list of screens (routes) and the bindings that create each screen's controller.
lib/core/configenv.dart reads API_BASE_URL from assets/.env.
lib/core/constantsColors (app_colors.dart), text styles, spacing, corner radius, shadows, image and icon paths, route names and shared text.
lib/core/themeapp_theme.dart: the light and dark themes built from the constants.
lib/core/networkThe API client (api_client.dart), the list of API addresses (api_endpoints.dart) and the response format.
lib/core/servicesSign-in token storage, saved preferences, push notifications, file picking, sharing, opening links and the video player.
lib/core/errorTurns network and server errors into the messages people see.
lib/core/ui, lib/core/utilsNavigation and snackbar helpers, and safe reading of JSON values.
lib/shared/widgetsWidgets used on many screens: cards, buttons, search field, logo, icons, and the loading, empty and error views.
lib/features/<feature>One folder per part of the app: auth, splash, home, dashboard, courses, player, quiz, assignments, certificates, live_classes, notifications, profile and support.
…/<feature>/datadatasources call the API, models read its JSON, and repositories combine them for the rest of the feature.
…/<feature>/domainentities (the plain data the screens use), the repository interfaces, and logic such as filtering and progress.
…/<feature>/presentationbindings (create the controller), controllers (GetX state), screens, widgets, and the screen's text in a *_strings.dart file.
assets.env.example (API address), app_icon (launcher icon source), fonts/inter (Inter with its license) and icons (SVG icons).
android, iosPlatform projects: app name, package name and bundle ID, launcher icons, permissions and signing.
test189 tests, laid out like lib, plus architecture_test.dart, which checks that the layers above stay separate.

To add a screen, copy the layout of an existing feature: add its route name in lib/core/constants/app_routes.dart and register the screen and its binding in lib/app.dart.

Rename the app and package

App name

Package name (Android) and bundle ID (iOS)

Icon, colors and font

Release builds and signing

Android

  1. Create an upload key (keep this file and its passwords safe):
    keytool -genkey -v -keystore ~/upload-keystore.jks -keyalg RSA -keysize 2048 -validity 10000 -alias upload
  2. Create android/key.properties:
    storePassword=your-store-password
    keyPassword=your-key-password
    keyAlias=upload
    storeFile=/path/to/upload-keystore.jks
    storeFile is the full path to the keystore you created. On Windows, use forward slashes, for example C:/keys/upload-keystore.jks. Never commit key.properties or the keystore; both are already in android/.gitignore.

    You don't need to edit any Gradle file. android/app/build.gradle.kts already reads key.properties and signs release builds with it. Without the file, release builds fall back to the debug key, which Google Play does not accept.

    Release signing in android/app/build.gradle.kts
    Figure 33: signingConfigs reads key.properties; the release build type uses it.
  3. Build the app bundle for Google Play:
    flutter build appbundle --release

iOS

  1. Open ios/Runner.xcworkspace in Xcode, select the Runner target, and under Signing & Capabilities choose your own team and bundle ID.
  2. Push notifications need the Push Notifications capability, which requires a paid Apple Developer account. On a free personal team, remove Runner.entitlements from the target to build without push.
  3. Build the archive for App Store Connect:
    flutter build ipa --release

Push notifications (optional)

NexusLMS works without Firebase. Learners still see every notification in the app's notification list; Firebase adds pushes to the phone's lock screen.

1. Create a Firebase project

  1. Create a project in the Firebase console.
    Create a Firebase project
    Figure 34: Create a Firebase project and give it a name.
  2. Add an Android app with your package name (the same applicationId as above) and click Register app.
    Add Firebase to the Android app
    Figure 35: Register the Android app with your package name.
  3. Download google-services.json and put it in mobile/android/app/, next to build.gradle.kts.
    google-services.json location
    Figure 36: google-services.json goes in mobile/android/app/.
  4. Add an Apple app with your bundle ID, then download GoogleService-Info.plist into mobile/ios/Runner/.
    Add Firebase to the Apple app
    Figure 37: Register the Apple app with your bundle ID.
  5. For iOS, open Project settings → Cloud Messaging, select your Apple app and upload an APNs authentication key (.p8) from your Apple Developer account.
    Firebase Cloud Messaging settings
    Figure 38: Cloud Messaging settings: select the Apple app.
    Upload APNs authentication key
    Figure 39: Upload the APNs authentication key (development and production).

The build picks these files up automatically. Without them, the app builds and runs with push turned off.

2. Connect the server

  1. In the Firebase console, open Project settings → Service accounts and click Generate new private key (a JSON file). Keep this file private.
    Generate a Firebase service account key
    Figure 40: Generate the service-account key that the server uses to send pushes.
  2. In Admin → Settings → Firebase, enable push, upload or paste that JSON file, and choose which events send a push: course assignment, assignment grading, certificates and live class reminders.

External services

ServiceWhen it is contacted
Firebase Cloud Messaging (fcm.googleapis.com, oauth2.googleapis.com)Only when push notifications are configured.
Your mail server (SMTP)Password reset and email notifications.
YouTube (youtube-nocookie.com) and Vimeo (player.vimeo.com)When a learner opens a video lesson hosted there. Uploaded video files are served by your own server.
Meeting and video linksLive class links (Zoom, Teams, Google Meet) and recordings open the provider's site or app.
Costs of third-party services: these services run on your own accounts, and you are responsible for any costs they charge. This includes your Firebase project (Cloud Messaging usage beyond Google's free tier), your SMTP or email provider, and any YouTube, Vimeo, Zoom, Teams or Google Meet plans you use. The NexusLMS price covers the source code only.

Troubleshooting

ProblemSolution
Blank page or "500 Server Error"Check storage/logs/laravel.log. Make sure storage and bootstrap/cache are writable and that composer install finished.
Styles are missingRun npm ci && npm run build so that public/build exists.
Uploaded images or files return 404Run php artisan storage:link. If your host does not allow symbolic links, ask your hosting provider to enable them.
Password reset emails do not arriveCheck the email settings and your mail provider's logs.
"Too many attempts"Sign-in allows 5 attempts per minute for each email address and network address. Wait a minute and try again.
The app cannot reach the serverCheck API_BASE_URL in assets/.env. Release builds need https://.
No push notificationsCheck the Firebase files, the service-account key in Admin → Settings, the event switches, and (iOS) the APNs key. Push does not work on the iOS simulator without APNs.
Live class or due date reminders are not sentMake sure the cron entry is installed. Due date reminders also need the switch under Settings → Security & Compliance.

Frequently asked questions

Does it run on shared (cPanel) hosting?

Yes, as long as the host offers PHP 8.3+, MySQL, a cron job and symbolic links (for php artisan storage:link). You can run composer install and npm run build on your own computer and upload the result if the host has no terminal. A VPS works too.

Do I need a queue worker or Redis?

No. Emails and push notifications are sent right after each request finishes, so only the cron job is needed.

Is the mobile app required?

No. Learners can do everything in the browser through the learner portal. The app is an extra way to learn on the phone.

Do I need Firebase?

Only for push notifications. Without Firebase, the app and the website work normally and people still get email and in-app notifications. See Push notifications.

Can learners sign up by themselves?

No, this is a company platform: admins add people under Admin → Users. When you add one person you choose their first password and they get a welcome email; people added by CSV import get an email with a link to choose their own password.

How do I point the app at my server?

Set API_BASE_URL in main/mobile/assets/.env to your site's address followed by /api/v1, then stop and run the app again. See Mobile app setup.

How do I change the name, logo and colors?

For the website, use Admin → Settings → General & Branding (see White-labeling). For the app, see Rename the app and package and Icon, colors and font.

Should I import the demo data on my live site?

No. Demo data is for trying the platform: the sample accounts have default passwords that are the same on every installation. Leave it off in the installer, or delete those accounts before you invite real people.

Support

If you run into a problem or have a question, many answers are already in Troubleshooting & FAQ.

For anything else, use the Support tab on the NexusLMS item page on CodeCanyon. Item support follows Envato's item support policy: questions about the item and fixes for reported bugs. Customization, installation on your servers, and third-party services such as your mail provider, Firebase, Apple and Google Play accounts are outside item support.

To help us answer quickly, tell us:

Credits and licenses

Server

PackageVersionLicense
Laravel Framework13.40MIT
Laravel Sanctum4.3MIT
Laravel Tinker3.0MIT
spatie/laravel-permission8.5MIT
Alpine.js3.17MIT
Tailwind CSS4.3MIT
Vite and laravel-vite-plugin8.3 / 3.2MIT
Fonts Inter, Playfair Display, Cinzel, Great Vibes and JetBrains Mono (bundled in public/fonts, licenses in the OFL-*.txt files there)–SIL Open Font License 1.1

Mobile app

PackageVersionLicense
Flutter3.44BSD-3-Clause
get4.7.3MIT
dio5.11.1MIT
cached_network_image4.0.3MIT
file_picker13.3.2MIT
firebase_core5.1.0BSD-3-Clause
firebase_messaging17.0.1BSD-3-Clause
flutter_dotenv6.0.1MIT
flutter_secure_storage11.2.0BSD-3-Clause
flutter_svg2.3.2MIT
flutter_widget_from_html_core0.17.4MIT
intl0.20.2BSD-3-Clause
share_plus13.3.1BSD-3-Clause
shared_preferences2.5.6BSD-3-Clause
url_launcher6.3.3BSD-3-Clause
video_player2.14.1BSD-3-Clause
webview_flutter4.14.1BSD-3-Clause
Inter font (bundled, license in assets/fonts/inter/OFL.txt)4.1SIL Open Font License 1.1
Material Symbols icons by Google (SVG files in assets/icons, license in assets/icons/LICENSE-material-symbols.txt)–Apache License 2.0

AI disclosure

AI tools (Claude by Anthropic) were used to help create this item's code, documentation and graphics, including the demo course artwork and the preview images. The author reviewed, edited and tested all of it; the screenshots show the real, working product.

Changelog

1.0.0