How janufniarz/symbiot works
Project Type and Purpose
• This is a full-stack, modular system named “symbiot” composed of:
• A Flutter-based front-end (“symbiot_flutter”) delivering UI for chat, operations, settings, etc.
• A Python API server (“symbiot_server”) exposing REST endpoints and persisting data.
• A Python engine service (“symbiot_engine”) encapsulating core control logic, handlers, and connectors.
• A shared Python library (“symbiot_lib”) providing common components (endpoints, division logic, tool kits).
• A scraper module (“github_pretrained”) for pretraining data extraction from GitHub.
• PowerShell scripts and Docker compose for build, configuration, and deployment.
File-Structure Analysis
• Top-Level:
• docker-compose.yml — orchestration of services (server, engine, DB).
• symbiot_flutter/ — Flutter app (lib/, windows/, pubspec).
• symbiot_server/ — Python API server (config, control, database, endpoints, scrapers).
• symbiot_engine/ — Python engine (config, connection, control, run_engine).
• symbiot_lib/ — shared Python library (components, objects, tool_kits).
• github_pretrained/ — Scrapy project for GitHub crawling.
• Patterns:
• API-based layering in server (endpoints → control/services → repositories → DB).
• Engine uses handler-middleware pattern (endpoints → handlers → connectors).
• Shared library for reusable division and endpoint abstractions.
Key Insights from README
• The README only gives the project name; architecture must be inferred from structure.
• Docker compose suggests containerized deployment of server, engine, and likely a database.