Classic crontabs
================

cronstable runs plain Vixie-style crontabs as-is, next to (or instead of) its
YAML configs. This directory is a runnable config dir mixing both formats.

Files
-----

  legacy.crontab   a classic crontab straight out of man 5 crontab:
                   NAME=value assignments, CRON_TZ, @nicknames, \% escapes
  dashboard.yaml   a native YAML job plus the web dashboard, loaded from
                   the same directory to show the two formats side by side

Try it
------

  # from the repository root:
  cronstable -c example/crontab

  # every legacy.crontab entry is an ordinary cronstable job named
  # legacy.crontab:<line number>; watch them all (YAML and crontab alike)
  # in the dashboard:
  #   http://localhost:8080/

  # a single crontab also works with no YAML at all:
  cronstable -c example/crontab/legacy.crontab

What to notice
--------------

  - Crontab entries get cronstable's standard defaults, not a cron emulation:
    schedules run in UTC unless CRON_TZ says otherwise, failure means a
    nonzero exit or stderr output (MAILTO is exported but sends no mail),
    and uncaptured stdout passes through to cronstable's own stdout -- so the
    crontab echoes land in your terminal, while the YAML job (with
    captureStdout: true) shows its output in the dashboard's log tail.

  - The moment an entry needs retries, reporting, timeouts, or any other
    per-job option, move it to YAML. Both formats can coexist in one
    directory for as long as a migration takes.

Full details and every deviation from cron:
https://github.com/ptweezy/cronstable/wiki/Classic-Crontabs