How lhaseparth2610/eduliteos works
Project type and purpose
• EduLite OS is a custom, Ubuntu-based Linux distribution optimized for low-end hardware, with a lightweight desktop (LXQt) and a suite of offline educational apps (Python scripts, Kolibri, teacher dashboards, exam mode, chatbot demos).
• It’s not a conventional client-server app but rather a full-stack OS distribution: from kernel and system services up through the desktop environment to individual educational applications.
File structure
• Top-level files: LICENSE, README.md, video/, ss/ (screenshots), simulated logs (exam_mode_simulation.log, etc.)
• apps/ – contains all of the custom Python educational applications:
• chatbot.py, 2ndchatbot.py, welcome.py, todo.py, test.py, exam_mode.py, lab_mode.py, reset.py
• model_data/ – serialized QA data (pickles, FAISS index) and CSVs for facts
• general_facts.csv, coding_facts.csv for content feeds
• test_jsons/ – sample test definitions used by exam_mode
• The README also describes system installation paths under /usr/local/share/edu_apps/, /usr/local/bin/, and desktop entries in /usr/share/applications/edu-os/.
Extract additional architecture insights from the README
• Base OS: Xubuntu (Linux kernel + system services + apt package manager + systemd + zram tuning)
• Desktop: LXQt
• Offline services: Kolibri integrated as a separate service
• Custom Python apps launched via symlinks and .desktop files
• Performance optimizations and low-RAM tuning (zram, minimal daemons)
a. Main components
• Hardware Layer (Low-end PCs ≤2 GB RAM)
• Kernel & System Services (Linux kernel, systemd, zram module)
• Package Manager & OS Layer (apt, Xubuntu base)
• Desktop Environment (LXQt window manager, panel, file manager)
• Offline Learning Service (Kolibri server process)
• Custom Python Apps (each script under apps/, reading from model_data/, CSVs, test_jsons/)
• Teacher Dashboard & Exam Mode Service (exam_mode.py + test_jsons)
• Data Layer (local pickles, FAISS index, CSVs, logs)
• Launcher & Integration (symlinks in /usr/local/bin, .desktop files in /usr/share/applications)
• User Interface (graphical menus, LXQt shortcuts)
b. Component relationships & data flow
• LXQt → Launcher Symlink (invokes the relevant Python script via PATH)
• Python App → Data Layer (loads pickles, FAISS index, CSVs, JSON tests)
• Python App → Writes logs (exam_mode_simulation.log, lab_mode_simulation.log)
• Apps → (optionally) Kolibri (for content served via local web UI)
• Systemd / services manage Kolibri and any background daemons (zram, tune scripts)
c. Architectural patterns & design principles
• Layered Architecture: Hardware → Kernel → OS → Desktop → Applications
• Single-responsibility apps: each Python script handles a distinct learning mode
• Shared data “library” (model_data) reused by multiple apps (chatbot & QA)
• Symlink + .desktop files act as the “API” / interface between desktop and apps
d. Key technologies & frameworks
• Linux kernel, systemd, zram
• apt package manager
• LXQt
• Python 3 scripts, FAISS, pickle, CSV, JSON
• Kolibri offline server