How zzyss-marker/newinno works
Project Type and Purpose
• This is a full-stack laboratory reservation system consisting of:
• A FastAPI-based RESTful backend (app/)
• A Flask-based administrative web app (admin_system/)
• A WeChat Mini-Program frontend (fore/)
• A SQLite persistence layer
File Structure
• Top-level directories:
• app/ – Main backend (FastAPI)
• admin_system/ – Admin UI (Flask)
• fore/ – WeChat mini-program client
• doc/ – Architecture and command docs
• test/ – Test scripts (locust load tests, test user creation)
• Key config/build files:
• requirements.txt – Python dependencies
• run.py – Launcher for FastAPI service
• admin_system/run.py – Launcher for Flask admin
• fore/project.config.json – Mini-program project config
README
• Confirms the above stack and outlines:
• User authentication flows
• Reservation workflows (venues, equipment, 3D printers)
• Admin features (approval, user/device management, data export)
• Tech requirements (Python 3.8+, FastAPI, Flask, SQLite, WeChat dev tools)
Main Components
a. WeChat Mini-Program (fore/)
– Pages: login, venue/equipment/3D-printer reservation, approvals, history
– Utilities: API client (fore/utils/request.js)
b. API Layer (app/)
– FastAPI entrypoint (app/main.py)
– Routers for auth, admin approval, management, reservations
– Business logic & validation (app/utils/)
– Data models & schemas (SQLAlchemy models & Pydantic schemas)
c. Admin Web App (admin_system/)
– Flask app (admin_system/app/routes & templates)
– Static assets & CSS for admin UI
– User/device/reservation management pages
d. Database(s)
– Primary SQLite (app.db) used by FastAPI
– Admin SQLite (e.g., admin.db) used by Flask app
– Schema creation scripts in app/db/ and admin_system/create_admin.py
e. External Tools
– Uvicorn/ASGI server for FastAPI
– Locust for performance testing (test/locustfile.py)
– WeChat Developer Tools for front-end
Relationships & Data Flows
• The Mini-Program issues HTTP(S) requests to the FastAPI server (/api/* endpoints).
• The FastAPI service uses SQLAlchemy to read/write the primary SQLite database.
• The Flask-based Admin UI runs separately (e.g., on port 5000), reads/writes its own admin database, and may call the same or separate tables for user/device management.
• Both services enforce authentication & authorization (role-based) via tokens or sessions.
Architectural Patterns & Principles
• Layered architecture:
• Presentation layer (WeChat UI & Flask admin UI)
• Application/API layer (FastAPI routers, business logic)
• Data access layer (SQLAlchemy models, DB scripts)
• Separation of concerns:
• Frontend vs. backend vs. admin UI
• Validation & security in utils/ modules
• Microservices-style separation: two independent services (FastAPI + Flask) connected to their respective data stores.
Technologies & Frameworks
• FastAPI, Uvicorn, SQLAlchemy, SQLite
• Flask, Jinja2 templates, CSS
• WeChat Mini-Program SDK, JavaScript, WXML/WXSS
• Locust for load testing
Essential Elements
• Component labels (e.g., “FastAPI Main”, “SQLAlchemy ORM”, “Venue Router”)
• Annotations for major frameworks and languages
• Callouts for important config files (e.g., config.py, config.js)