Skip to content

[Price Compare] Step 8: Configure Railway cron for daily report #79

@frankieboxx

Description

@frankieboxx

Step 8 — Cron Configuration

Option A — Separate Railway cron service (preferred)

  • Script: scripts/price_compare.py
  • Cron: 0 9 * * * (09:00, after 08:00 crawl)
  • Env vars needed: DB_DSN, ATRIUM_DATABASE_URL, MAILGUN_API_KEY, MAILGUN_DOMAIN, REPORT_RECIPIENTS

Option B — Add to existing crawl pipeline

  • Append to crawl-and-import.sh after crawler finishes
  • Pro: single service; Con: couples concerns

Decision: Option A (separate cron) — preferred for isolation.

Priority: P3

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions