How aharneish/daily-job-digest works
Project Type and Purpose
• This is an automation/batch-job project (not a full-stack web app).
• It runs on a schedule (GitHub Actions) or manually and collects job listings to send a daily email digest.
Main Components
a. Scheduler
• GitHub Actions workflow (cron + manual trigger).
b. Execution Environment
• GitHub runner (Ubuntu) OR local developer machine OR Docker container.
c. Application Code
• Entry points: daily_job_digest.py (main digest logic) and main.py (utilities/CLI).
• Internal module: Job-bot/ (helper functions, scrapers).
d. Data Store
• Static CSV: job_listings.csv.
e. External Services
• LinkedIn (job scraping via session cookie).
• Gmail SMTP (send email via GMAIL_USER/GMAIL_PASS).
f. Configuration
• Environment variables (.env or CI secrets).
• render.yaml, pyproject.toml, requirements.txt, lock files.
Relationships and Data Flows
• Scheduler → clones repo → spins up runner/container
• Runner/container → installs dependencies → executes daily_job_digest.py
• Script → reads job_listings.csv → optionally scrapes LinkedIn (using LINKEDIN_SESSION_COOKIE) → aggregates listings
• Script → connects to Gmail SMTP → sends digest email to recipients
• Workflow logs/results return to GitHub Actions for audit
Architectural Patterns & Design Principles
• Batch-processing pipeline (ETL-style): Extract (CSV + scraping), Transform (aggregate/filter), Load (email).
• Twelve-factor app principles for config via environment variables.
• Containerization for environment consistency.
Technologies & Frameworks
• Python 3.x
• GitHub Actions (YAML workflow)
• Docker (Dockerfile.dockerfile)
• Gmail SMTP
• CSV file I/O, HTTP scraping (inside Job-bot module)
Final Composition
• Middle layer:
• Code components:
– daily_job_digest.py
– Job-bot/ library
– main.py (utility entry)
• Footer: optional “Developer Machine” path replicating the Runner/Container flow.