Graham McIntire
e99bf06eb4
Previous commit (3c988a5f) switched oban_pro to the licensed hex repo at deploy time. Reverting that — keep all three Pro packages vendored so prod image builds don't depend on oban.pro reachability or auth on every CI run. oban_pro 1.7.0 dropped into vendor/oban_pro via `mix hex.package fetch oban_pro 1.7.0 --repo=oban --unpack`. mix.exs goes back to `path: "vendor/oban_pro"` (matching oban_met / oban_web, which were already vendored — and stay vendored since the licensed repo only has older versions of those: 0.1.11 / 2.10.6 vs the 1.1.0 / 2.12.1 we vendor). Schema migration from3c988a5fstays — 1.7.0 tables/indexes are already applied. No code changes.
9 lines
560 B
Markdown
9 lines
560 B
Markdown
# Rules for Using Oban Pro
|
|
|
|
Oban Pro is a commercial extension to Oban that provides advanced job processing features for
|
|
Elixir applications. It adds composition primitives (workflows, batches, chains, chunks), smart
|
|
concurrency controls (global limits, rate limiting), and enhanced worker capabilities (structured
|
|
args, encryption, deadlines, hooks). Read the reference files before writing Oban Pro code. Do not
|
|
assume standard Oban patterns apply. Pro has its own idioms and best practices.
|
|
|
|
For full documentation: https://oban.pro/docs/pro/overview.html
|