:verbose: true
# We set concurrency to 1 because parts of the publishing pipeline
# are not threadsafe. Once we've removed instances of `I18n.with_locale`
# from the workers, we can increase this again.
:concurrency: 1
:logfile: ./log/sidekiq.json.log
:queues:
  - scheduled_publishing
  - default
  - publishing_api
  - email_alert_api_signup
  - bulk_republishing
  - sync_checks
  - asset_migration
  - link_checks
:schedule:
  check_all_organisations_links_worker:
    cron: '0 2 * * *' # Runs 2 a.m.
    class: CheckAllOrganisationsLinksWorker

:verbose: true
# We set concurrency to 1 because parts of the publishing pipeline
# are not threadsafe. Once we've removed instances of `I18n.with_locale`
# from the workers, we can increase this again.
:concurrency: 1
:logfile: ./log/sidekiq.json.log
:queues:
  - scheduled_publishing
  - default
  - publishing_api
  - email_alert_api_signup
  - bulk_republishing
  - sync_checks
  - link_checks
  - asset_migration
:schedule:
  check_all_organisations_links_worker:
    cron: '0 2 * * *' # Runs 2 a.m.
    class: CheckAllOrganisationsLinksWorker

Move asset_migration queue to the lowest priority
Move asset_migration queue to the lowest priority

We're about to migrate about 1.5m attachments from Whitehall to Asset
Manager and we think this might take a few days (partly because our
Sidekiq config defines a concurrency of 1). This would block any
`link_checks` jobs (currently scheduled at about 2am each day) from
running until all the assets have migrated. Moving the asset_migration
queue to the bottom of the list will ensure that Sidekiq will only
process our jobs once the other queues are empty.
