How nikdanilov/flask-react-todo-app works
Project type and purpose
• This is a full‑stack To‑Do web application.
• Front‑end: React & Redux SPA, bundled by Webpack, written in ES6+/SCSS.
• Back‑end: Python Flask REST API, JWT authentication, SQLAlchemy ORM, MySQL database.
• Database migration via Alembic.
File structure
• Top‑level:
• application/ – Flask app modules (app.py routes, models.py ORM models, utils/auth.py JWT helpers).
• migrations/ – Alembic config & versioned migration scripts.
• static/ – front‑end source: webpack configs, package.json, React/Redux code under src/, SCSS, images, test config.
• config.py – database connection string.
• manage.py – CLI for DB creation and running the server.
• tests/ & test.py – pytest tests for API endpoints and models.
• Patterns:
• Backend: MVC/Blueprint style, utility module for auth.
• Frontend: Redux folder structure: actions, reducers, components, containers, store config, utils.
• Build scripts: Webpack splits dev/prod configs, Babel, ESLint, SCSS loader.
README for additional insights
• Confirms separation: front‑end (npm/React) vs back‑end (pip/Flask).
• Technology stack: Flask + SQLAlchemy + MySQL, React/Redux + React‑Router, Material‑UI, Webpack.
Elements
• Clear labels: “React SPA”, “Flask REST API”, “MySQL DB”, “Alembic Migration Service”.
• From Browser → API (HTTP/JSON).
• From API → DB (SQL via SQLAlchemy).
• From CLI (manage.py) → DB (CREATE TABLE via ORM).
• Hexagon or gear for build tools (Webpack/Alembic).