Jamil 4a448e5517 fix(portal): separate dev and runtime Oban configs (#10027) ...

Oban includes its own configuration validation, which seems to prevent
`runtime.exs` from overriding any compile-time options. This prevents us
from using ENV vars to configure it, such as restricting job execution
to `domain` nodes by setting `queues: []`. To fix that, we make sure to
set Oban configuration in env-specific files `config/dev.exs` and
`config/test.exs`, and at runtime for prod with `config/runtime.exs`.

Fixes #10016

2025-07-28 15:13:52 +00:00

..

config.exs

fix(portal): separate dev and runtime Oban configs (#10027)

2025-07-28 15:13:52 +00:00

dev.exs

fix(portal): separate dev and runtime Oban configs (#10027)

2025-07-28 15:13:52 +00:00

prod.exs

fix(portal): groom resource list and flows periodically (#10005)

2025-07-25 21:04:41 +00:00

runtime.exs

fix(portal): separate dev and runtime Oban configs (#10027)

2025-07-28 15:13:52 +00:00

test.exs

fix(portal): separate dev and runtime Oban configs (#10027)

2025-07-28 15:13:52 +00:00