How urbao/stockoala works
Main Components
a. CLI Launcher
• run.sh (Linux) / stockoala.exe (Windows)
• stockoala.desktop (Linux desktop integration)
b. Configuration Loader
• src/config.py + src/config.json
c. Data Collector & Scraper
• src/collect.py
• src/stock_scraper.py (interacts with TWSE & TPEX via requests & bs4)
d. Data Storage (Local FS)
• weekly-data/ (text files)
• monthly-data/ (text + JSON files)
e. Data Combiner
• src/data_combiner.py (merges raw daily files into period aggregates)
f. Analyzers
• src/weekly_analyze.py (reverse‐point strategy)
• src/monthly_analyze.py (low‐price strategy)
• src/analyze.py + src/analyze_helper.py (common logic)
g. Output & Reporting
• src/output.py (console & file output)
h. Core Orchestrator
• src/main.py (invokes the above modules in sequence)
Relationships & Data Flows
– CLI Launcher invokes main.py
– main.py loads config → triggers collect → scraper fetches data → raw files written under weekly‐data/ & monthly‐data/
– data_combiner reads raw files → produces combined data structures
– analyzers consume combined data → compute signals
– output writes results to console or local report files
Architectural Patterns & Principles
• Modular layering: separate concerns for configuration, data collection, merging, analysis, and output.
• Local‐first storage: all data persists in file directories for privacy.
• Single‐process, script‐driven orchestration via Python CLI.
Incorporate Key Technologies
• Language & Runtime: Python 3.x
• HTTP & Parsing: requests, BeautifulSoup (bs4)
• CLI UX: colorama
• Shell Integration: Bash script & desktop entry (Linux)
– Arrowheads marking data direction (e.g., read vs. write)
– Annotations for protocols (e.g., HTTP GET to TWSE/TPEX)
– Boundaries: group all Python modules under a “Stockoala Core” boundary