glitch-social/config/sidekiq.yml

---
:concurrency: 5
:queues:
  - default
  - push
  - pull
  - mailers
:schedule:
  subscriptions_scheduler:
    cron: '0 5 * * *'
    class: Scheduler::SubscriptionsScheduler
  media_cleanup_scheduler:
    cron: '5 4 * * *'
    class: Scheduler::MediaCleanupScheduler
  feed_cleanup_scheduler:
    cron: '0 0 * * *'
    class: Scheduler::FeedCleanupScheduler
Adjust down the number of Sidekiq threads to 5 (default of 25 is way too high) 2016-03-25 13:20:31 +00:00			`---`
			`:concurrency: 5`
More robust PuSH subscription refreshes (#2799) * Fix #2473 - Use sidekiq scheduler to refresh PuSH subscriptions instead of cron Fix an issue where / in domain would raise exception in TagManager#normalize_domain PuSH subscriptions refresh done in a round-robin way to avoid hammering a single server's hub in sequence. Correct handling of failures/retries through Sidekiq (see also #2613). Optimize Account#with_followers scope. Also, since subscriptions are now delegated to Sidekiq jobs, an uncaught exception will not stop the entire refreshing operation halfway through Fix #2702 - Correct user agent header on outgoing http requests * Add test for SubscribeService * Extract #expiring_accounts into method * Make mastodon:push:refresh no-op * Queues are now defined in sidekiq.yml * Queues are now in sidekiq.yml 2017-05-05 01:23:01 +01:00			`:queues:`
			`- default`
			`- push`
			`- pull`
			`- mailers`
			`:schedule:`
			`subscriptions_scheduler:`
			`cron: '0 5 * * *'`
			`class: Scheduler::SubscriptionsScheduler`
Replace mastodon:media:clear and mastodon:feeds:clear rake tasks with (#3180) sidekiq-scheduler jobs Resolves #2495 2017-05-20 18:42:58 +01:00			`media_cleanup_scheduler:`
			`cron: '5 4 * * *'`
			`class: Scheduler::MediaCleanupScheduler`
			`feed_cleanup_scheduler:`
			`cron: '0 0 * * *'`
			`class: Scheduler::FeedCleanupScheduler`