render.yaml

# Blueprint for the two services that can be declared today: the database and the
# cron trigger.
#
# Blueprints do not yet support Workflow services, so the Workflow itself is
# created separately (Dashboard → New → Workflow, same repo). This is a two-step
# setup, not a one-click deploy — see "Deploy" in the README.

databases:
  - name: sync-db
    databaseName: sync
    user: sync
    plan: basic-256mb
    postgresMajorVersion: "17"
    # Same region as the Workflow service, so it is reachable over the private
    # network and DATABASE_URL can stay internal.
    region: oregon

services:
  - type: cron
    name: api-sync-trigger
    runtime: python
    plan: starter
    region: oregon
    # Every 30 minutes. Anything shorter than SYNC_OVERLAP_SECONDS (300s) mostly
    # re-syncs the overlap buffer; the upsert makes that safe, just wasteful.
    schedule: "*/30 * * * *"
    buildCommand: pip install -r requirements.txt
    startCommand: python cron/trigger.py
    envVars:
      # Set both of these by hand after creating the Workflow service: the task
      # slug does not exist until the Workflow does.
      - key: RENDER_API_KEY
        sync: false
      - key: WORKFLOW_TASK_SLUG
        sync: false
      - key: POLL_INTERVAL_SECONDS
        value: "30"
      # Watch a little past run_sync's own 3600s task timeout, so the run's
      # timeout is always what resolves it rather than the watcher giving up.
      - key: MAX_WAIT_SECONDS
        value: "5400"