How yuno-mi/community works
1. This repository is a small Python automation project, archived as a learning record rather than an active product. The architecture is centered on backend job execution, not on a UI or public web API.
2. The top-level entrypoint is main.py. It is the application boundary that likely coordinates which service job runs, making it the main place an engineer would look to understand execution flow.
3. Business logic is split into the services/ package. The service modules are task-oriented and appear to represent separate automation jobs:
- facilitator_daily.py for a daily workflow/reporting task
- delete_bot_message.py for cleanup or maintenance of bot-posted messages
- token_check.py for validating or monitoring authentication state
4. Shared integration code lives under lib/. This is the lower-level support layer that the services depend on, rather than each service talking directly to external systems.
5. lib/wrike_api.py is the primary integration boundary. It likely encapsulates all communication with Wrike, so external API calls are centralized instead of duplicated across services.
6. lib/config.py is the configuration boundary. It probably loads environment-specific settings such as API tokens, workspace IDs, or runtime flags, keeping secrets and deployment-specific values out of the service logic.
7. The overall data flow is simple: main.py selects a service, the service executes the job logic, and the service uses lib/wrike_api.py plus configuration from lib/config.py to interact with Wrike or related automation targets.
8. There is no sign of a database, message queue, or frontend in the file tree. That suggests a lightweight, stateless worker-style design where each run performs a task and exits, with state managed externally by the integrated service.
9. Docker is part of the deployment boundary. The presence of both Dockerfile and docker-compose.yml indicates the project is intended to run in a containerized environment, likely for repeatable local execution or scheduled deployment.
10. requirements.txt defines the Python runtime dependencies, which makes the project a self-contained script/service package rather than a larger framework-based application.
11. In an architecture diagram, the key elements would be: the Python application container, main.py as the entrypoint, services/ as the job layer, lib/ as the shared integration/config layer, and Wrike as the external system on the other side of the API boundary.
12. The most important architectural distinction is between orchestration and integration: services/ contains the “what to do” logic, while lib/ contains the “how to talk to Wrike” mechanics. That separation is the main design feature visible from the repository structure.
Main entry points: services services · config.py Config · wrike_api.py Wrike API · facilitator_daily.py Daily job
Components 12
Application
Python entrypoint and runtime boundary
- main.py · Application entrypoint that selects and runs a service job
main.py
Job Services
Task-oriented automation jobs
- services · Task-oriented automation workflows
services - Daily job · Daily facilitator workflow and reporting task
services/facilitator_daily.py - Cleanup job · Removes or cleans up bot-posted messages
services/delete_bot_message.py - Token check · Validates or monitors authentication state
services/token_check.py
Shared Lib
Configuration and external integration layer
Deployment
Containerized execution assets
- Dockerfile · Container image definition for repeatable execution
Dockerfile - Compose · Containerized local or scheduled execution setup
docker-compose.yml - Dependencies · Python package dependencies for the automation runtime
requirements.txt
External Systems
Third-party service boundary
- Wrike · External system reached through the shared API layer
Connections 15
- Dockerfile → main.py: runs · Builds a container that executes the entrypoint
- Compose → Dockerfile: uses · Orchestrates the containerized runtime
- Dependencies → main.py: supports · Defines the Python runtime dependencies
- main.py → services: selects job · Entry point dispatches to a service workflow
- services → Daily job: contains · Package groups the daily automation job
- services → Cleanup job: contains · Package groups the cleanup job
- services → Token check: contains · Package groups the auth-monitoring job
- Daily job → Config: reads · Uses shared runtime settings
- Daily job → Wrike API: calls · Relies on the centralized Wrike integration
- Cleanup job → Config: reads · Uses shared runtime settings
- Cleanup job → Wrike API: calls · Relies on the centralized Wrike integration
- Token check → Config: reads · Uses shared runtime settings
- Token check → Wrike API: calls · Relies on the centralized Wrike integration
- Config → Wrike: configures · Provides credentials and environment values for API access
- Wrike API → Wrike: integrates · All Wrike communication is centralized here