How mattiasaan/landesk works
Project type and purpose
• This is a full-stack Progressive Web App (PWA) called “LANdesk,” consisting of:
• A Python backend (in backend_py) exposing REST-style endpoints for user auth, notes, tasks, file uploads/downloads, and user addition.
• A static web UI (in web_ui) built with HTML, CSS, and vanilla JS that registers a service worker and a manifest for offline support.
• The README simply names the project; the file tree shows its note-/task-management focus plus file handling.
File structure
• Top-level directories:
• backend_py: modules (add_user.py, auth.py, files.py, notes.py, tasks.py), plus generators (note_sender, task_sender) and main.py.
• web_ui: static assets (HTML pages, scripts per page, style.css, manifest.json, service-worker.js, images).
• No explicit “database” directory—data is likely persisted via file system or an embedded DB accessed by files.py.
• The presence of main.py implies a monolithic Python web server (e.g., Flask, FastAPI, or similar).
• The service-worker.js and manifest.json signal a PWA caching layer for offline use.
README for additional insights
• Rely on file names and PWA files to infer layers: UI layer, client-side caching layer, server layer, data-store layer.
Detail without overcomplicating
• Python module as its own subcomponent under Business Logic.
• Explicit fetch/XHR calls from each JS controller to its corresponding API endpoint.
• Service-worker intercept path for both static assets and API calls (if the PWA caches API responses).